Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 92bd1993af21305f103e4fb697ed949f2866c37a36b9c8ccfe5bdcaeff0781ff

Tx prefix hash: 1d341579363d49538bc1d0f3c468a6c3e2ea10f31bf98f93cff3faf2b712a36c
Tx public key: 337682754fca42de213f8d6521a45a92dc6f7f0ff59bcb284205f508bbd67157
Timestamp: 1771681044 Timestamp [UTC]: 2026-02-21 13:37:24 Age [y:d:h:m:s]: 00:270:10:46:48
Block: 1482668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198836 RingCT/type: yes/0
Extra: 01337682754fca42de213f8d6521a45a92dc6f7f0ff59bcb284205f508bbd67157021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 395a20a87cd68a392b1718c17fda05ed62609a7b1eae4c81709eac0da621683e 0.000600000000 1972062 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1482678, "vin": [ { "gen": { "height": 1482668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "395a20a87cd68a392b1718c17fda05ed62609a7b1eae4c81709eac0da621683e" } } ], "extra": [ 1, 51, 118, 130, 117, 79, 202, 66, 222, 33, 63, 141, 101, 33, 164, 90, 146, 220, 111, 127, 15, 245, 155, 203, 40, 66, 5, 245, 8, 187, 214, 113, 87, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: