Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac873c20ef8509513236207e4aa1ccacee0ed2e5f812fe583a47707ff1832358

Tx prefix hash: 8589427fff02ebd203b1aac0906029f5379da4aafa6b7ee11437ce85a3e5ce43
Tx public key: a7e12ebbc7bd0d85e2ca47f3c082c4c3a910f6259307e067195f97743004ec2a
Timestamp: 1730660989 Timestamp [UCT]: 2024-11-03 19:09:49 Age [y:d:h:m:s]: 00:081:00:30:43
Block: 1145860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57920 RingCT/type: yes/0
Extra: 01a7e12ebbc7bd0d85e2ca47f3c082c4c3a910f6259307e067195f97743004ec2a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1479ad5e5d58036bb4aa4cabd5fdd93020658767752b9e298e401634805a9cd1 0.600000000000 1630385 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": 1145870, "vin": [ { "gen": { "height": 1145860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1479ad5e5d58036bb4aa4cabd5fdd93020658767752b9e298e401634805a9cd1" } } ], "extra": [ 1, 167, 225, 46, 187, 199, 189, 13, 133, 226, 202, 71, 243, 192, 130, 196, 195, 169, 16, 246, 37, 147, 7, 224, 103, 25, 95, 151, 116, 48, 4, 236, 42, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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