Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d40989bde27b5ee23ea0f0bdca420851d90ed90c5642f12874e4b66a00d75dba

Tx prefix hash: d66fb9c21985d76a501f8340bf928e516c94d272c4f1ca598304c412d1b086dc
Tx public key: f2e5064bd7eb6e15bf3c8fc193d7b505804d6f1c9b1db696573b9da3d24747a9
Timestamp: 1713109401 Timestamp [UCT]: 2024-04-14 15:43:21 Age [y:d:h:m:s]: 00:270:13:31:57
Block: 1000409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193688 RingCT/type: yes/0
Extra: 01f2e5064bd7eb6e15bf3c8fc193d7b505804d6f1c9b1db696573b9da3d24747a902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2850c302fdd5f795e63d8d13b531d3e33ec769a97f5d3a91fea0487e0a120e91 0.600000000000 1460907 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": 1000419, "vin": [ { "gen": { "height": 1000409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2850c302fdd5f795e63d8d13b531d3e33ec769a97f5d3a91fea0487e0a120e91" } } ], "extra": [ 1, 242, 229, 6, 75, 215, 235, 110, 21, 191, 60, 143, 193, 147, 215, 181, 5, 128, 77, 111, 28, 155, 29, 182, 150, 87, 59, 157, 163, 210, 71, 71, 169, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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