Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970c928e4a89a0bcc03bf6395e1298be81f8a8c0f9ac70c5a91f293f09c84017

Tx prefix hash: 78e3e33cc837a056270027225ae79cebf3df20e662acb31a01908bd07f82e579
Tx public key: ccc484e889c207e26a25330451fcfbcb6235c8b2568535b3577d1520dfd66496
Timestamp: 1715454727 Timestamp [UCT]: 2024-05-11 19:12:07 Age [y:d:h:m:s]: 00:327:09:57:04
Block: 1019901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233998 RingCT/type: yes/0
Extra: 01ccc484e889c207e26a25330451fcfbcb6235c8b2568535b3577d1520dfd6649602110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b40281177b1c5eafeb8d3d6eeba2bdaa69e610daa35210579daec0f3f5a20cc0 0.600000000000 1483954 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": 1019911, "vin": [ { "gen": { "height": 1019901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b40281177b1c5eafeb8d3d6eeba2bdaa69e610daa35210579daec0f3f5a20cc0" } } ], "extra": [ 1, 204, 196, 132, 232, 137, 194, 7, 226, 106, 37, 51, 4, 81, 252, 251, 203, 98, 53, 200, 178, 86, 133, 53, 179, 87, 125, 21, 32, 223, 214, 100, 150, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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