Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38aac68946b84b185858c656ae8160cfdd865a0cd3c41e2b2f57d90a64768452

Tx prefix hash: 9d5ede83802ea14c2c2a3823d2e2d661cc004ea73983968b0bdec8aaea955c54
Tx public key: 7dbd53ec64fa1aed590a5546eaf0cc76d4f5c1385cb12d9e5d17626134578a2e
Timestamp: 1704440221 Timestamp [UCT]: 2024-01-05 07:37:01 Age [y:d:h:m:s]: 01:307:00:43:46
Block: 928535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478275 RingCT/type: yes/0
Extra: 017dbd53ec64fa1aed590a5546eaf0cc76d4f5c1385cb12d9e5d17626134578a2e0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dbc660342056a9c5159268117a64f9ca87a14818e5dbf9b1e923b52e31a154b 0.600000000000 1386395 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": 928545, "vin": [ { "gen": { "height": 928535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dbc660342056a9c5159268117a64f9ca87a14818e5dbf9b1e923b52e31a154b" } } ], "extra": [ 1, 125, 189, 83, 236, 100, 250, 26, 237, 89, 10, 85, 70, 234, 240, 204, 118, 212, 245, 193, 56, 92, 177, 45, 158, 93, 23, 98, 97, 52, 87, 138, 46, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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