Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32b068a4c141e85ce3b352e967253a29493f0ad078491fd2185ee1884908c0bf

Tx prefix hash: b63b7f5289ba209a05603afb96f66d955484fbb35ea71c0d2945f6cbcc0712d6
Tx public key: 077e53f73949bcb418f96920beb2743dc3aafa5dd5788470fc6a25e817cacbe5
Timestamp: 1736436258 Timestamp [UCT]: 2025-01-09 15:24:18 Age [y:d:h:m:s]: 00:159:21:13:47
Block: 1193682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113977 RingCT/type: yes/0
Extra: 01077e53f73949bcb418f96920beb2743dc3aafa5dd5788470fc6a25e817cacbe502110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c9f82dbed24eaa5f385c3edac39d01aa054b9b936875f4a8bf005359f39eef6 0.600000000000 1680245 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": 1193692, "vin": [ { "gen": { "height": 1193682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c9f82dbed24eaa5f385c3edac39d01aa054b9b936875f4a8bf005359f39eef6" } } ], "extra": [ 1, 7, 126, 83, 247, 57, 73, 188, 180, 24, 249, 105, 32, 190, 178, 116, 61, 195, 170, 250, 93, 213, 120, 132, 112, 252, 106, 37, 232, 23, 202, 203, 229, 2, 17, 0, 0, 0, 11, 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