Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c3fed1ac00078614c657f44824d3a9450e76b98ae9f0a151b260f7d7b19a48

Tx prefix hash: a7d36fd6350ca42f5ba79bcaf1ffacb18c759f308b937baff4b3b09f98016ae7
Tx public key: 397df39cd3eadb4a4a09bb345d05c315e9312be8acfeddc959ab44f6e17ebfa5
Timestamp: 1712136919 Timestamp [UCT]: 2024-04-03 09:35:19 Age [y:d:h:m:s]: 00:296:14:18:50
Block: 992330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212294 RingCT/type: yes/0
Extra: 01397df39cd3eadb4a4a09bb345d05c315e9312be8acfeddc959ab44f6e17ebfa502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aec19dbbb7bbf9ec5264329f0016dfc1b38a4623749cd78dc2f1edd4259729e1 0.600000000000 1452670 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": 992340, "vin": [ { "gen": { "height": 992330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aec19dbbb7bbf9ec5264329f0016dfc1b38a4623749cd78dc2f1edd4259729e1" } } ], "extra": [ 1, 57, 125, 243, 156, 211, 234, 219, 74, 74, 9, 187, 52, 93, 5, 195, 21, 233, 49, 43, 232, 172, 254, 221, 201, 89, 171, 68, 246, 225, 126, 191, 165, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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