Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4637d300545ecc70bf8e1339f422beea94649520d4bb4eabd0ff16f763af5e1

Tx prefix hash: 65736a23c56f3cfd38fd00fb0e7b5e4c070c023a910c05c8630459b5bc24dacc
Tx public key: 18a926371cd24ef945e91627a92aff291679ddc7c9fcf9a7744925a154820381
Timestamp: 1729907305 Timestamp [UCT]: 2024-10-26 01:48:25 Age [y:d:h:m:s]: 00:153:19:49:45
Block: 1139657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109729 RingCT/type: yes/0
Extra: 0118a926371cd24ef945e91627a92aff291679ddc7c9fcf9a7744925a1548203810211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c3facdbd8d8f95f8464ce0acc6d2d8da81a60c5fbf6ef732102ddb6dc94660 0.600000000000 1623444 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": 1139667, "vin": [ { "gen": { "height": 1139657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c3facdbd8d8f95f8464ce0acc6d2d8da81a60c5fbf6ef732102ddb6dc94660" } } ], "extra": [ 1, 24, 169, 38, 55, 28, 210, 78, 249, 69, 233, 22, 39, 169, 42, 255, 41, 22, 121, 221, 199, 201, 252, 249, 167, 116, 73, 37, 161, 84, 130, 3, 129, 2, 17, 0, 0, 0, 4, 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