Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca5217e174d12032d4d943c3fbce3b221991e25c0fa241c5db7d6ff9c4f7d4e4

Tx prefix hash: a903867e50f75c2574f0e2a80d6328adf47b2e973243e811ee78440fe987f26f
Tx public key: c36ae340ff7ca161c939b146fadd82e883dc0f555d12addc98d256d84238458a
Timestamp: 1708942919 Timestamp [UCT]: 2024-02-26 10:21:59 Age [y:d:h:m:s]: 01:083:15:56:34
Block: 965895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320836 RingCT/type: yes/0
Extra: 01c36ae340ff7ca161c939b146fadd82e883dc0f555d12addc98d256d84238458a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a46f2e6b96ac7d4952d2e5090a597f19a79c4797d72107d691911d941f8330 0.600000000000 1425650 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": 965905, "vin": [ { "gen": { "height": 965895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a46f2e6b96ac7d4952d2e5090a597f19a79c4797d72107d691911d941f8330" } } ], "extra": [ 1, 195, 106, 227, 64, 255, 124, 161, 97, 201, 57, 177, 70, 250, 221, 130, 232, 131, 220, 15, 85, 93, 18, 173, 220, 152, 210, 86, 216, 66, 56, 69, 138, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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