Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cda6018ddce2157fd0f592fa15858536a1d8ed1938bc654c97d7b5f3b3174c85

Tx prefix hash: 7947f2933d2a3dfd91a7955cc5498884413f42f94cf9ea2b632055e816b30679
Tx public key: 596d9f3c4df0127e4dc8e8c5ea7ee948f99f825e11e1ef3b1b5d77e3dec1b5ed
Timestamp: 1706470002 Timestamp [UCT]: 2024-01-28 19:26:42 Age [y:d:h:m:s]: 01:103:21:47:44
Block: 945362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335368 RingCT/type: yes/0
Extra: 01596d9f3c4df0127e4dc8e8c5ea7ee948f99f825e11e1ef3b1b5d77e3dec1b5ed02110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b79d739103d4b930dbf8c3b1c68d43d65091c875d4f859a018da89e53f6610e 0.600000000000 1403674 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": 945372, "vin": [ { "gen": { "height": 945362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b79d739103d4b930dbf8c3b1c68d43d65091c875d4f859a018da89e53f6610e" } } ], "extra": [ 1, 89, 109, 159, 60, 77, 240, 18, 126, 77, 200, 232, 197, 234, 126, 233, 72, 249, 159, 130, 94, 17, 225, 239, 59, 27, 93, 119, 227, 222, 193, 181, 237, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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