Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7a364e8ef0599d812d6ff11d50c09f117e959a9f4b026394cac10111b9477b2

Tx prefix hash: 4c3b17887d93877b036cfd3b1640fe6a9d52c9dcf0bf38592e84088cbe205ad4
Tx public key: dd8389c6179759340750885e4d66774a089dfaac1d4a7ec14e473d243dd90cd8
Timestamp: 1731720262 Timestamp [UCT]: 2024-11-16 01:24:22 Age [y:d:h:m:s]: 00:141:02:51:48
Block: 1154638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100669 RingCT/type: yes/0
Extra: 01dd8389c6179759340750885e4d66774a089dfaac1d4a7ec14e473d243dd90cd80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 219c9513d8b1623b2c876381daf929d871670675103b72dc4c3deb8cae74b61e 0.600000000000 1640251 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": 1154648, "vin": [ { "gen": { "height": 1154638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "219c9513d8b1623b2c876381daf929d871670675103b72dc4c3deb8cae74b61e" } } ], "extra": [ 1, 221, 131, 137, 198, 23, 151, 89, 52, 7, 80, 136, 94, 77, 102, 119, 74, 8, 157, 250, 172, 29, 74, 126, 193, 78, 71, 61, 36, 61, 217, 12, 216, 2, 17, 0, 0, 0, 6, 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