Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 690a64c1e8115f927cad1a287f3fb7bcca56c16cc141f69e3e74305aa5ea130f

Tx prefix hash: a304a58ea7883f4a51e011cfe409f0c1939e06ff80a68f00982aa7cc43e9afb4
Tx public key: c4290bea94dc096771fc3ba0a3d74e146277a046ce5cfa7ba0911ca65bccaa3c
Timestamp: 1762036864 Timestamp [UCT]: 2025-11-01 22:41:04 Age [y:d:h:m:s]: 00:004:23:34:30
Block: 1402943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3562 RingCT/type: yes/0
Extra: 01c4290bea94dc096771fc3ba0a3d74e146277a046ce5cfa7ba0911ca65bccaa3c0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 758413c40b2c59bded5c898bbec41013cd1e643cc4fff386c9c710ffb838200b 0.600000000000 1891268 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": 1402953, "vin": [ { "gen": { "height": 1402943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "758413c40b2c59bded5c898bbec41013cd1e643cc4fff386c9c710ffb838200b" } } ], "extra": [ 1, 196, 41, 11, 234, 148, 220, 9, 103, 113, 252, 59, 160, 163, 215, 78, 20, 98, 119, 160, 70, 206, 92, 250, 123, 160, 145, 28, 166, 91, 204, 170, 60, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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