Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5d8dbc1a71518d2981d9e70319d9111d3dd561a8a6bb8c5bb820a7be982a99

Tx prefix hash: 2410c09dc1428fd202c3b34120bb2551e4b8c8dc7303a1f52dbd14e990494cf0
Tx public key: 3a96d48de6fe1953f74aec064248a23cd1918bb8856532c7422bc3aa95b0b06d
Timestamp: 1717065453 Timestamp [UCT]: 2024-05-30 10:37:33 Age [y:d:h:m:s]: 00:154:08:54:02
Block: 1033231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110488 RingCT/type: yes/0
Extra: 013a96d48de6fe1953f74aec064248a23cd1918bb8856532c7422bc3aa95b0b06d02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac78c456897b64f56ff8dee8f72d4d0b3d9b52c0a8102e529b7d858cbb8caa97 0.600000000000 1501694 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": 1033241, "vin": [ { "gen": { "height": 1033231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac78c456897b64f56ff8dee8f72d4d0b3d9b52c0a8102e529b7d858cbb8caa97" } } ], "extra": [ 1, 58, 150, 212, 141, 230, 254, 25, 83, 247, 74, 236, 6, 66, 72, 162, 60, 209, 145, 139, 184, 133, 101, 50, 199, 66, 43, 195, 170, 149, 176, 176, 109, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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