Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96db844b75f939487d85c16d867fd15387e6fbfc16f72cdcd5107b5043ad0b7c

Tx prefix hash: 89a621c63f78fe9e21133b1c5bd08a76be822ba745eacdf17b6b189a7769a886
Tx public key: a5683c40d70004af8bcdacf5663e47b51ac6fea90fc28f36d25897485cb07f38
Timestamp: 1701501824 Timestamp [UCT]: 2023-12-02 07:23:44 Age [y:d:h:m:s]: 01:163:10:14:34
Block: 904192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377991 RingCT/type: yes/0
Extra: 01a5683c40d70004af8bcdacf5663e47b51ac6fea90fc28f36d25897485cb07f3802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.619493185000 dcy

stealth address amount amount idx
00: 1c9e4d45d93f3da7c373e8b452377c3e58af8959d5e8f794e8304f536c28a134 0.619493185000 1360903 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": 904202, "vin": [ { "gen": { "height": 904192 } } ], "vout": [ { "amount": 619493185, "target": { "key": "1c9e4d45d93f3da7c373e8b452377c3e58af8959d5e8f794e8304f536c28a134" } } ], "extra": [ 1, 165, 104, 60, 64, 215, 0, 4, 175, 139, 205, 172, 245, 102, 62, 71, 181, 26, 198, 254, 169, 15, 194, 143, 54, 210, 88, 151, 72, 92, 176, 127, 56, 2, 17, 0, 0, 0, 2, 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