Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c22d3f7ecb5a964a51236f84b96ea10a60812ec0112e26078f08dfea7f65a569

Tx prefix hash: cb7399385e104ceee935982761ae63857d0be3db224a0647fd1264ddd59f2a3c
Tx public key: 5313682ae910008d3aa7f7c1fd03ef178b99dec393e3f70c5385a327cac660de
Timestamp: 1697394606 Timestamp [UCT]: 2023-10-15 18:30:06 Age [y:d:h:m:s]: 02:039:00:22:25
Block: 870359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547502 RingCT/type: yes/0
Extra: 015313682ae910008d3aa7f7c1fd03ef178b99dec393e3f70c5385a327cac660de02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.801935347000 dcy

stealth address amount amount idx
00: d48c1269a9572f0e852a3869280fbeb230ec9d38c9372e375fe9af92a8b13567 0.801935347000 1325238 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": 870369, "vin": [ { "gen": { "height": 870359 } } ], "vout": [ { "amount": 801935347, "target": { "key": "d48c1269a9572f0e852a3869280fbeb230ec9d38c9372e375fe9af92a8b13567" } } ], "extra": [ 1, 83, 19, 104, 42, 233, 16, 0, 141, 58, 167, 247, 193, 253, 3, 239, 23, 139, 153, 222, 195, 147, 227, 247, 12, 83, 133, 163, 39, 202, 198, 96, 222, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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