Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f41c102bbb62fcecd9e57f7d41d1db033ff2428d0b6dffa134a560aa1dc66cf

Tx prefix hash: fd6e66ac776455c53e1394bf38354c53a0fad210384e87f3d7cb71bee58d7dcc
Tx public key: 2f1c0e8736ec21db3048bc7f9aeabadf8a94dd118d244e2966a7cb7fe4fccce2
Timestamp: 1761746404 Timestamp [UCT]: 2025-10-29 14:00:04 Age [y:d:h:m:s]: 00:008:11:43:25
Block: 1400556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6046 RingCT/type: yes/0
Extra: 012f1c0e8736ec21db3048bc7f9aeabadf8a94dd118d244e2966a7cb7fe4fccce20211000000158368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 459e6e67d4bf7ae535c9a5ff2e3046cadab54be0d2dcb4313376b1dab146e3be 0.600000000000 1888867 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 dinasty-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": 1400566, "vin": [ { "gen": { "height": 1400556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "459e6e67d4bf7ae535c9a5ff2e3046cadab54be0d2dcb4313376b1dab146e3be" } } ], "extra": [ 1, 47, 28, 14, 135, 54, 236, 33, 219, 48, 72, 188, 127, 154, 234, 186, 223, 138, 148, 221, 17, 141, 36, 78, 41, 102, 167, 203, 127, 228, 252, 204, 226, 2, 17, 0, 0, 0, 21, 131, 104, 38, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8