Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e57bf98dc37645920fc7391478660d42ed4bfcfb5ee30c032e6aaf793c07d5d7

Tx prefix hash: eb2ac4ecc98c648bf049eaabb6a20de42420c90ceffc98e8f955a47fdaaba1e9
Tx public key: eb78e2ffcbdb4d9867267ae675016e308bc3d211fad5ec7c220317d5b0a7e301
Timestamp: 1744710650 Timestamp [UCT]: 2025-04-15 09:50:50 Age [y:d:h:m:s]: 00:268:22:31:39
Block: 1261915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190012 RingCT/type: yes/0
Extra: 01eb78e2ffcbdb4d9867267ae675016e308bc3d211fad5ec7c220317d5b0a7e301021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59b35ddbc5146f42f0e57ba1c514e8c8c9021729b1688898f823374c80251b20 0.600000000000 1749090 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": 1261925, "vin": [ { "gen": { "height": 1261915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59b35ddbc5146f42f0e57ba1c514e8c8c9021729b1688898f823374c80251b20" } } ], "extra": [ 1, 235, 120, 226, 255, 203, 219, 77, 152, 103, 38, 122, 230, 117, 1, 110, 48, 139, 195, 210, 17, 250, 213, 236, 124, 34, 3, 23, 213, 176, 167, 227, 1, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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