Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf7bdb7c142d74c31263c54cecba984e31bd347c96f205c3c02569d66576ef3e

Tx prefix hash: 3aa938adaf916e45a33ba7d86e155921b9e16ad1edc79d144b468ee17be26799
Tx public key: a9495a248e896015e28e26ce821b592e0c78c8ea91b62c2ee564212ab92b33b7
Timestamp: 1741390108 Timestamp [UTC]: 2025-03-07 23:28:28 Age [y:d:h:m:s]: 01:254:12:17:19
Block: 1234429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445928 RingCT/type: yes/0
Extra: 01a9495a248e896015e28e26ce821b592e0c78c8ea91b62c2ee564212ab92b33b7021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 192678eef7c97bf067a9a7aebc11e56eb48fb4608039cd1148a016f68a13ec57 0.000600000000 1721356 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": 1234439, "vin": [ { "gen": { "height": 1234429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "192678eef7c97bf067a9a7aebc11e56eb48fb4608039cd1148a016f68a13ec57" } } ], "extra": [ 1, 169, 73, 90, 36, 142, 137, 96, 21, 226, 142, 38, 206, 130, 27, 89, 46, 12, 120, 200, 234, 145, 182, 44, 46, 229, 100, 33, 42, 185, 43, 51, 183, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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: