Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0cd1cb5b789a1be191131a49678a558f33dc1a330a332ecb89416e8be1658b7

Tx prefix hash: 031d732b8083bca8c98ae0bc24504a81b49aeb18d5d44df87c0943ced69177b8
Tx public key: e6065c0ff5e41b1d1f5c1c2469bfdd40fab0a57201f451b8ff4865ee6a70ab34
Timestamp: 1764714800 Timestamp [UCT]: 2025-12-02 22:33:20 Age [y:d:h:m:s]: 00:001:16:33:06
Block: 1425138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1223 RingCT/type: yes/0
Extra: 01e6065c0ff5e41b1d1f5c1c2469bfdd40fab0a57201f451b8ff4865ee6a70ab340211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 800a2531b8465be71f21c99aaf47d57a86c6d83718b6cd2bc962877fa644d4c8 0.600000000000 1913771 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": 1425148, "vin": [ { "gen": { "height": 1425138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "800a2531b8465be71f21c99aaf47d57a86c6d83718b6cd2bc962877fa644d4c8" } } ], "extra": [ 1, 230, 6, 92, 15, 245, 228, 27, 29, 31, 92, 28, 36, 105, 191, 221, 64, 250, 176, 165, 114, 1, 244, 81, 184, 255, 72, 101, 238, 106, 112, 171, 52, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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