Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac7911811a0c23138999ffcea45905ce5902d96ad8e1090a0db3dcd1ed8a8cb7

Tx prefix hash: 5cc0b17cf1dc015c2ac340f74ad58dd68a896f3c8d9deeb2255780b05908df78
Tx public key: 5acd719dc43e7c8d7adf88e6e03626ff9ccac9fcc5e2a8b7ceb89080972fc2b7
Timestamp: 1709209621 Timestamp [UCT]: 2024-02-29 12:27:01 Age [y:d:h:m:s]: 01:099:15:58:34
Block: 968105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332278 RingCT/type: yes/0
Extra: 015acd719dc43e7c8d7adf88e6e03626ff9ccac9fcc5e2a8b7ceb89080972fc2b70211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24b10bf5eb8e79497c9cdf36e99adac6a350bd47f534a249302634b6f1b7d5d3 0.600000000000 1427904 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": 968115, "vin": [ { "gen": { "height": 968105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24b10bf5eb8e79497c9cdf36e99adac6a350bd47f534a249302634b6f1b7d5d3" } } ], "extra": [ 1, 90, 205, 113, 157, 196, 62, 124, 141, 122, 223, 136, 230, 224, 54, 38, 255, 156, 202, 201, 252, 197, 226, 168, 183, 206, 184, 144, 128, 151, 47, 194, 183, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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