Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b23f12886eb46392f64f3adf30dffec5cdf6beaf990824363e14f56d823cbc49

Tx prefix hash: 5464f5d13b818ab268863e4cff4c9fbd3f0855d2d666f791a83381be44c8cefe
Tx public key: 32a8af1ab724723ddfbd778f2933094b5a85c5c7337f34d026973e1b2544298a
Timestamp: 1764956157 Timestamp [UTC]: 2025-12-05 17:35:57 Age [y:d:h:m:s]: 00:156:06:44:04
Block: 1427128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104352 RingCT/type: yes/0
Extra: 0132a8af1ab724723ddfbd778f2933094b5a85c5c7337f34d026973e1b2544298a021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 03cad25298a1970de126bdd4f936e4c31ce53e5fd0cfc1cdfd1da56beac469c1 0.000600000000 1915827 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": 1427138, "vin": [ { "gen": { "height": 1427128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03cad25298a1970de126bdd4f936e4c31ce53e5fd0cfc1cdfd1da56beac469c1" } } ], "extra": [ 1, 50, 168, 175, 26, 183, 36, 114, 61, 223, 189, 119, 143, 41, 51, 9, 75, 90, 133, 197, 199, 51, 127, 52, 208, 38, 151, 62, 27, 37, 68, 41, 138, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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: