Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edd34a89f5f7bd5345b1bbd54b21bfd022afafab34590b854901e2e5e5e839cb

Tx prefix hash: d51b4fe94cebf2a7c0e7ef66d61375e253381613179393f96f0b150c56fb9d4c
Tx public key: 39a70ad2dc9e2fd85f40d42e1d40c0617eb6cfac47a9776d3733dc44a8fc28af
Timestamp: 1730623452 Timestamp [UCT]: 2024-11-03 08:44:12 Age [y:d:h:m:s]: 00:065:13:24:34
Block: 1145544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46906 RingCT/type: yes/0
Extra: 0139a70ad2dc9e2fd85f40d42e1d40c0617eb6cfac47a9776d3733dc44a8fc28af0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b106683476ff956d366254035495fc02cff8cb309f38f1860184a416b140988 0.600000000000 1629997 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": 1145554, "vin": [ { "gen": { "height": 1145544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b106683476ff956d366254035495fc02cff8cb309f38f1860184a416b140988" } } ], "extra": [ 1, 57, 167, 10, 210, 220, 158, 47, 216, 95, 64, 212, 46, 29, 64, 192, 97, 126, 182, 207, 172, 71, 169, 119, 109, 55, 51, 220, 68, 168, 252, 40, 175, 2, 17, 0, 0, 0, 2, 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