Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e23050983d99da724607af9e790e07d625e35807370ce4e26e85c502d89902d9

Tx prefix hash: 9d8ba341fbafa3804574b40e0a3662a7ec829d2d8286d3b6c89148a2d2b4e74c
Tx public key: c81c57c135ae4d88ce462c365b310552e8080f9c695066e9b0ef5bdaaab9838f
Timestamp: 1711190047 Timestamp [UCT]: 2024-03-23 10:34:07 Age [y:d:h:m:s]: 01:268:17:14:58
Block: 984541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450763 RingCT/type: yes/0
Extra: 01c81c57c135ae4d88ce462c365b310552e8080f9c695066e9b0ef5bdaaab9838f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e8e31d818de24a88a3badcf1da0a5b689315b41f3039db5e347abe4e27ab210 0.600000000000 1444712 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": 984551, "vin": [ { "gen": { "height": 984541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e8e31d818de24a88a3badcf1da0a5b689315b41f3039db5e347abe4e27ab210" } } ], "extra": [ 1, 200, 28, 87, 193, 53, 174, 77, 136, 206, 70, 44, 54, 91, 49, 5, 82, 232, 8, 15, 156, 105, 80, 102, 233, 176, 239, 91, 218, 170, 185, 131, 143, 2, 17, 0, 0, 0, 3, 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