Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdcb8f6218e7337379ba2c93c7047eab0bf05bc5ebe4b86839a5c7495d93f8d3

Tx prefix hash: 53e9764868612d033072e811827be8684743fcef89877ea0f932708db7b8a159
Tx public key: e84afdd90d87941350c19ddab2c439c5d2e7fd5e6f6a4ae1cbae28ae47daa65d
Timestamp: 1737222117 Timestamp [UCT]: 2025-01-18 17:41:57 Age [y:d:h:m:s]: 00:337:12:40:11
Block: 1200149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238809 RingCT/type: yes/0
Extra: 01e84afdd90d87941350c19ddab2c439c5d2e7fd5e6f6a4ae1cbae28ae47daa65d0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61b51ade9882648b837f1a1ea5fdb5623aa23944b2d48ebe2265fd2ca849be88 0.600000000000 1686790 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": 1200159, "vin": [ { "gen": { "height": 1200149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61b51ade9882648b837f1a1ea5fdb5623aa23944b2d48ebe2265fd2ca849be88" } } ], "extra": [ 1, 232, 74, 253, 217, 13, 135, 148, 19, 80, 193, 157, 218, 178, 196, 57, 197, 210, 231, 253, 94, 111, 106, 74, 225, 203, 174, 40, 174, 71, 218, 166, 93, 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