Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd339896ccfe0f49218581ca6b5ecb7c45d6d007af09c71b66d6dd6ece0ba101

Tx prefix hash: 63509c8a9025b7b18dfc8ceea0d585fddf4c4251e49af5803fc5b63f9b9731dc
Tx public key: a54638eb88d2f1a314bb834ece284b68c2306d078f4290433961d903b448dd41
Timestamp: 1676334014 Timestamp [UCT]: 2023-02-14 00:20:14 Age [y:d:h:m:s]: 02:053:05:47:44
Block: 696434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559635 RingCT/type: yes/0
Extra: 01a54638eb88d2f1a314bb834ece284b68c2306d078f4290433961d903b448dd41021100000001b2a2997d000000000000000000

1 output(s) for total of 3.022908300000 dcy

stealth address amount amount idx
00: 5aa1145f0237cbcd2c29b94ea4297002b346a93bb3691f7de8b3f599416a20e7 3.022908300000 1139439 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": 696444, "vin": [ { "gen": { "height": 696434 } } ], "vout": [ { "amount": 3022908300, "target": { "key": "5aa1145f0237cbcd2c29b94ea4297002b346a93bb3691f7de8b3f599416a20e7" } } ], "extra": [ 1, 165, 70, 56, 235, 136, 210, 241, 163, 20, 187, 131, 78, 206, 40, 75, 104, 194, 48, 109, 7, 143, 66, 144, 67, 57, 97, 217, 3, 180, 72, 221, 65, 2, 17, 0, 0, 0, 1, 178, 162, 153, 125, 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