Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b39237ec4437ea2e72caa627de870ea193783c2c929bed02bbcf716484f4198

Tx prefix hash: e7b76767bb2716a7503b4f9fd4d0f5a09156b9149a93ca3f4508e41628d93c34
Tx public key: b6c22b3fb10892a0c39152ffad7cdd4dc8d4da2aa83b94f462511a951f17dad6
Timestamp: 1736020155 Timestamp [UCT]: 2025-01-04 19:49:15 Age [y:d:h:m:s]: 00:169:19:29:40
Block: 1190238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120967 RingCT/type: yes/0
Extra: 01b6c22b3fb10892a0c39152ffad7cdd4dc8d4da2aa83b94f462511a951f17dad602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 002bb25255944aeb560d46f952888b729f5c056a07996c8fdc9887ffb51be021 0.600000000000 1676753 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": 1190248, "vin": [ { "gen": { "height": 1190238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "002bb25255944aeb560d46f952888b729f5c056a07996c8fdc9887ffb51be021" } } ], "extra": [ 1, 182, 194, 43, 63, 177, 8, 146, 160, 195, 145, 82, 255, 173, 124, 221, 77, 200, 212, 218, 42, 168, 59, 148, 244, 98, 81, 26, 149, 31, 23, 218, 214, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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