Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0adbc190be6223f1ce46d6d5414665d92498e30cd235989ddd13c799735fc12

Tx prefix hash: b17234a0b8c77bc0723c64e8152273a58b9c50323ab80edd50c2a975055e5f42
Tx public key: 40cb43269a2a7a2e1d9c93a444b7d8f352fe5d9840dbca75f7de0c757a4f322d
Timestamp: 1639126368 Timestamp [UCT]: 2021-12-10 08:52:48 Age [y:d:h:m:s]: 03:139:15:31:12
Block: 392379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 878560 RingCT/type: yes/0
Extra: 0140cb43269a2a7a2e1d9c93a444b7d8f352fe5d9840dbca75f7de0c757a4f322d021100000002d6e4826b000000000000000000

1 output(s) for total of 30.752884088000 dcy

stealth address amount amount idx
00: e7a7dd2562e0d8613a8d8f6d742e40aecfa6209fa32d6482f4305267b5e0dc15 30.752884088000 789222 of 0

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": 392389, "vin": [ { "gen": { "height": 392379 } } ], "vout": [ { "amount": 30752884088, "target": { "key": "e7a7dd2562e0d8613a8d8f6d742e40aecfa6209fa32d6482f4305267b5e0dc15" } } ], "extra": [ 1, 64, 203, 67, 38, 154, 42, 122, 46, 29, 156, 147, 164, 68, 183, 216, 243, 82, 254, 93, 152, 64, 219, 202, 117, 247, 222, 12, 117, 122, 79, 50, 45, 2, 17, 0, 0, 0, 2, 214, 228, 130, 107, 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