Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3e918ec89e259f23839466dcb34d9349ed4f851943f4e6321859d1eea7b59f0

Tx prefix hash: 9dfc966683bfde8c46f3c86cf696ad86dc2a63b1b0dff4cb206693b960b113da
Tx public key: cb4ce32d64e86c5f3c5e0381aa46a46270b6696d28441c187bdb828ca098a92d
Timestamp: 1710401192 Timestamp [UCT]: 2024-03-14 07:26:32 Age [y:d:h:m:s]: 01:021:21:48:02
Block: 978001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276615 RingCT/type: yes/0
Extra: 01cb4ce32d64e86c5f3c5e0381aa46a46270b6696d28441c187bdb828ca098a92d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd52cb35a11be6cfb9f65a9840b6dd0dacc195c221989a77713f0e6eb8900784 0.600000000000 1438010 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": 978011, "vin": [ { "gen": { "height": 978001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd52cb35a11be6cfb9f65a9840b6dd0dacc195c221989a77713f0e6eb8900784" } } ], "extra": [ 1, 203, 76, 227, 45, 100, 232, 108, 95, 60, 94, 3, 129, 170, 70, 164, 98, 112, 182, 105, 109, 40, 68, 28, 24, 123, 219, 130, 140, 160, 152, 169, 45, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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