Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e98995ec56b479f635bfa343b92d7e5346dd9d8edf6b2ee1c480d9d87b464c2e

Tx prefix hash: bdfb6ac30c44ee3d8ba5d582057c99d0683f64e10e02b335ac691786d76bbf10
Tx public key: 026b84b9dc91ba5329764ee118e3b3206a99b55fefa96532d2a7775a4e43becb
Timestamp: 1714108025 Timestamp [UCT]: 2024-04-26 05:07:05 Age [y:d:h:m:s]: 00:203:05:41:31
Block: 1008705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145491 RingCT/type: yes/0
Extra: 01026b84b9dc91ba5329764ee118e3b3206a99b55fefa96532d2a7775a4e43becb02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fdea8a213ab13abb9e5c7f891a9634dfe272a7b635975c5ee4b09d001340f7f 0.600000000000 1470181 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": 1008715, "vin": [ { "gen": { "height": 1008705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fdea8a213ab13abb9e5c7f891a9634dfe272a7b635975c5ee4b09d001340f7f" } } ], "extra": [ 1, 2, 107, 132, 185, 220, 145, 186, 83, 41, 118, 78, 225, 24, 227, 179, 32, 106, 153, 181, 95, 239, 169, 101, 50, 210, 167, 119, 90, 78, 67, 190, 203, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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