Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76e2d4efd7c7ffb9f4bd993c4f5a702dd4bf54996a289c7373a40f094c341721

Tx prefix hash: 868d19f81ef73fad29a97f697f304321bd15843aadcf352c4ea537f0c151d7e3
Tx public key: dff69774bbb8b1109e27ae074adcb5126e8ef56641b535ba6cb736af9dcf9527
Timestamp: 1765058236 Timestamp [UCT]: 2025-12-06 21:57:16 Age [y:d:h:m:s]: 00:052:10:32:29
Block: 1427975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37375 RingCT/type: yes/0
Extra: 01dff69774bbb8b1109e27ae074adcb5126e8ef56641b535ba6cb736af9dcf9527021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 591a81e84ff909e1e8e82d6030e440026520eded833f503673a0b30f7dac7d64 0.600000000000 1916682 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": 1427985, "vin": [ { "gen": { "height": 1427975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "591a81e84ff909e1e8e82d6030e440026520eded833f503673a0b30f7dac7d64" } } ], "extra": [ 1, 223, 246, 151, 116, 187, 184, 177, 16, 158, 39, 174, 7, 74, 220, 181, 18, 110, 142, 245, 102, 65, 181, 53, 186, 108, 183, 54, 175, 157, 207, 149, 39, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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