Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa2e62193a461b91646f84f866be92ce4ea7b2b2e406c6910bb2410c3419981

Tx prefix hash: 98ae1e2a24c9d4dfd4d3517abc6c7d68f6e99ea913e7dc0b6def7b566bdd88a1
Tx public key: 543e6ac7af3ff64d3c8d7a6965c837f92514e6dd75fa0fbf11e7c8b2c2cb18c9
Timestamp: 1732327867 Timestamp [UCT]: 2024-11-23 02:11:07 Age [y:d:h:m:s]: 00:001:03:57:07
Block: 1159666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 825 RingCT/type: yes/0
Extra: 01543e6ac7af3ff64d3c8d7a6965c837f92514e6dd75fa0fbf11e7c8b2c2cb18c90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeb99543a262932e611bf3399bd2422b6bed49039bf6108b6194c51ed35a848b 0.600000000000 1645305 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": 1159676, "vin": [ { "gen": { "height": 1159666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeb99543a262932e611bf3399bd2422b6bed49039bf6108b6194c51ed35a848b" } } ], "extra": [ 1, 84, 62, 106, 199, 175, 63, 246, 77, 60, 141, 122, 105, 101, 200, 55, 249, 37, 20, 230, 221, 117, 250, 15, 191, 17, 231, 200, 178, 194, 203, 24, 201, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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