Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 456b3403475260e0c3540af8b4e86d4b1fcc86b3f081cf9a25c56dfaed900f4b

Tx prefix hash: 178bb22d14bd072498e66a290c6d9a0b821ae238ee9b501d86d6fe5776724121
Tx public key: cf4cbbd5601a63095ebe1a64f06f387984f41ade000895e946b024b4f4142ced
Timestamp: 1575035909 Timestamp [UCT]: 2019-11-29 13:58:29 Age [y:d:h:m:s]: 05:066:20:08:58
Block: 19731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190685 RingCT/type: yes/0
Extra: 01cf4cbbd5601a63095ebe1a64f06f387984f41ade000895e946b024b4f4142ced021100000004e37fbbaf000000000000000000

1 output(s) for total of 527.987795031000 dcy

stealth address amount amount idx
00: 6ba23c0ba8f2f2f302927933ee4d0e3b17385d9c339fb8963cd21726c5f46ab1 527.987795031000 31296 of 0

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": 19741, "vin": [ { "gen": { "height": 19731 } } ], "vout": [ { "amount": 527987795031, "target": { "key": "6ba23c0ba8f2f2f302927933ee4d0e3b17385d9c339fb8963cd21726c5f46ab1" } } ], "extra": [ 1, 207, 76, 187, 213, 96, 26, 99, 9, 94, 190, 26, 100, 240, 111, 56, 121, 132, 244, 26, 222, 0, 8, 149, 233, 70, 176, 36, 180, 244, 20, 44, 237, 2, 17, 0, 0, 0, 4, 227, 127, 187, 175, 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