Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 901ceaa0d2cd4a6eb5b154fbcec656b79c875f6b4af93824fcb3d635c983a660

Tx prefix hash: 0e31c8959baad293c7371350c450009c4e14e0935be65a61baecd7914e346e42
Tx public key: cb6597f5461e9c2e13c4ab9d1118e0ac87a52f3bace5b302be8d0fdcc36f9416
Timestamp: 1636726544 Timestamp [UCT]: 2021-11-12 14:15:44 Age [y:d:h:m:s]: 03:087:03:41:31
Block: 372850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 840678 RingCT/type: yes/0
Extra: 01cb6597f5461e9c2e13c4ab9d1118e0ac87a52f3bace5b302be8d0fdcc36f941602110000000b745f00f8000000000000000000

1 output(s) for total of 35.693863847000 dcy

stealth address amount amount idx
00: 0bf8d3a6696f1cbf5b15fd3b10af4eb0bd9d30b33256f7d96658affc92fdb8f6 35.693863847000 755178 of 0

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": 372860, "vin": [ { "gen": { "height": 372850 } } ], "vout": [ { "amount": 35693863847, "target": { "key": "0bf8d3a6696f1cbf5b15fd3b10af4eb0bd9d30b33256f7d96658affc92fdb8f6" } } ], "extra": [ 1, 203, 101, 151, 245, 70, 30, 156, 46, 19, 196, 171, 157, 17, 24, 224, 172, 135, 165, 47, 59, 172, 229, 179, 2, 190, 141, 15, 220, 195, 111, 148, 22, 2, 17, 0, 0, 0, 11, 116, 95, 0, 248, 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