Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e21fe0f192fe75f962be7620919d26403ec30f5e34a09da6fff2519fefd2d842

Tx prefix hash: 1ecc3f61a9626981863f59a0637be666cd3f2b55fc76ec687eaea2b699e48548
Tx public key: 5fc1611a58ae4f14613c4ec2db06c968873b6e54c67a51c019aa9cc1f94a4a94
Timestamp: 1696273952 Timestamp [UCT]: 2023-10-02 19:12:32 Age [y:d:h:m:s]: 01:149:08:58:23
Block: 861052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367775 RingCT/type: yes/0
Extra: 015fc1611a58ae4f14613c4ec2db06c968873b6e54c67a51c019aa9cc1f94a4a9402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.860948799000 dcy

stealth address amount amount idx
00: e1ab8a1e9b496004a7ef2ca872ff1dfd62892a72379d2b74e0a7089e609d4b5d 0.860948799000 1315364 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": 861062, "vin": [ { "gen": { "height": 861052 } } ], "vout": [ { "amount": 860948799, "target": { "key": "e1ab8a1e9b496004a7ef2ca872ff1dfd62892a72379d2b74e0a7089e609d4b5d" } } ], "extra": [ 1, 95, 193, 97, 26, 88, 174, 79, 20, 97, 60, 78, 194, 219, 6, 201, 104, 135, 59, 110, 84, 198, 122, 81, 192, 25, 170, 156, 193, 249, 74, 74, 148, 2, 17, 0, 0, 0, 1, 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