Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da38c8239ac2b3488000c0f7e276d2f509ad17e17ce219543815140e84ea7055

Tx prefix hash: 4860f82567f815fd3a94e93c6f85db5284e907b07db6637669c0d1d00a389263
Tx public key: e5a0dc1fda18ea63fbf68511cc12f4832357189ce28d7f915d753b297927eb27
Timestamp: 1737587570 Timestamp [UCT]: 2025-01-22 23:12:50 Age [y:d:h:m:s]: 00:297:03:15:20
Block: 1203168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209911 RingCT/type: yes/0
Extra: 01e5a0dc1fda18ea63fbf68511cc12f4832357189ce28d7f915d753b297927eb2702110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0300f7e36a0e2c29601ee751fb60966bff82489bdf19451cc216bc2a7ab625e 0.600000000000 1689841 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": 1203178, "vin": [ { "gen": { "height": 1203168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0300f7e36a0e2c29601ee751fb60966bff82489bdf19451cc216bc2a7ab625e" } } ], "extra": [ 1, 229, 160, 220, 31, 218, 24, 234, 99, 251, 246, 133, 17, 204, 18, 244, 131, 35, 87, 24, 156, 226, 141, 127, 145, 93, 117, 59, 41, 121, 39, 235, 39, 2, 17, 0, 0, 0, 10, 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