Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03c4af214b6ff9897fa2115875cf29fa3c4b7a0e33fd48bb6e8e867f584b6b2c

Tx prefix hash: 23b4f246bed2d415ebd138307157210b2f2c53bec6a6631cf889e482e7ae308e
Tx public key: 7b18bc31b0388607a2b57b8e434083da2d768fe5ef6dcfab2b505a6652c7274a
Timestamp: 1713952268 Timestamp [UCT]: 2024-04-24 09:51:08 Age [y:d:h:m:s]: 00:205:01:50:16
Block: 1007420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146799 RingCT/type: yes/0
Extra: 017b18bc31b0388607a2b57b8e434083da2d768fe5ef6dcfab2b505a6652c7274a02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9431b637e05222babd88d878d6599dbf38647f49048e2f15d5a935c73475316e 0.600000000000 1468752 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": 1007430, "vin": [ { "gen": { "height": 1007420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9431b637e05222babd88d878d6599dbf38647f49048e2f15d5a935c73475316e" } } ], "extra": [ 1, 123, 24, 188, 49, 176, 56, 134, 7, 162, 181, 123, 142, 67, 64, 131, 218, 45, 118, 143, 229, 239, 109, 207, 171, 43, 80, 90, 102, 82, 199, 39, 74, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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