Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344b51726dfcaf3865185645f2b0fc00ab20931c080749d2384509fe11f96787

Tx prefix hash: 47d68210700dcf989e609d57dd7169966299e6d750a76656ca5b571f5922b098
Tx public key: eccdc86f8b3c09254dfbc8b4cb65f2fe09096005a617f496114f24583a1c0b82
Timestamp: 1721561547 Timestamp [UCT]: 2024-07-21 11:32:27 Age [y:d:h:m:s]: 00:335:00:38:50
Block: 1070494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239245 RingCT/type: yes/0
Extra: 01eccdc86f8b3c09254dfbc8b4cb65f2fe09096005a617f496114f24583a1c0b82021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e22bc2490f1c4dc86b4ae3e840fd23f71700af8d59243a3ae77a9031c42d3c84 0.600000000000 1542351 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": 1070504, "vin": [ { "gen": { "height": 1070494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e22bc2490f1c4dc86b4ae3e840fd23f71700af8d59243a3ae77a9031c42d3c84" } } ], "extra": [ 1, 236, 205, 200, 111, 139, 60, 9, 37, 77, 251, 200, 180, 203, 101, 242, 254, 9, 9, 96, 5, 166, 23, 244, 150, 17, 79, 36, 88, 58, 28, 11, 130, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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