Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03283e70abfc8c977718a4196b9f030347806b485359b4142d731f49c38866d5

Tx prefix hash: 8602a9651653ee84efdcd32dc3ff6a728b9e78c42cb72a1be04d6dd3e8ea124e
Tx public key: 6d68b1ac8fed34e2f80fcc237ca1ad6fcb30bde06289857e9aa0b33b51c5b301
Timestamp: 1695642228 Timestamp [UCT]: 2023-09-25 11:43:48 Age [y:d:h:m:s]: 01:120:10:14:40
Block: 855816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347312 RingCT/type: yes/0
Extra: 016d68b1ac8fed34e2f80fcc237ca1ad6fcb30bde06289857e9aa0b33b51c5b301021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.896037889000 dcy

stealth address amount amount idx
00: 352da580c0ff6d6a69f14e79ca6f65cf66bb381c4818a6c80ed9d1c50b2ca5a3 0.896037889000 1309860 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": 855826, "vin": [ { "gen": { "height": 855816 } } ], "vout": [ { "amount": 896037889, "target": { "key": "352da580c0ff6d6a69f14e79ca6f65cf66bb381c4818a6c80ed9d1c50b2ca5a3" } } ], "extra": [ 1, 109, 104, 177, 172, 143, 237, 52, 226, 248, 15, 204, 35, 124, 161, 173, 111, 203, 48, 189, 224, 98, 137, 133, 126, 154, 160, 179, 59, 81, 197, 179, 1, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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