Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33fb3fcb23f431e87ec4217455e4dcdb5e1ad6205646e78e6982ec8ddc92723f

Tx prefix hash: 2b22bae6f79614f08ad8e4b8127d44cb18732cac865475662a091437d3a4ae54
Tx public key: e0a4d7782d439f243622579af7f8fe36410c91ebce610fb036387df8b1034cd5
Timestamp: 1760373378 Timestamp [UCT]: 2025-10-13 16:36:18 Age [y:d:h:m:s]: 00:074:18:48:01
Block: 1389162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53532 RingCT/type: yes/0
Extra: 01e0a4d7782d439f243622579af7f8fe36410c91ebce610fb036387df8b1034cd5021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6756154cf44fa2a2f311da28dc8f0475a2c6d893ec9bacf7a854383ac7962d5a 0.600000000000 1877391 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": 1389172, "vin": [ { "gen": { "height": 1389162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6756154cf44fa2a2f311da28dc8f0475a2c6d893ec9bacf7a854383ac7962d5a" } } ], "extra": [ 1, 224, 164, 215, 120, 45, 67, 159, 36, 54, 34, 87, 154, 247, 248, 254, 54, 65, 12, 145, 235, 206, 97, 15, 176, 54, 56, 125, 248, 177, 3, 76, 213, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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