Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67f4a9e6d452e29ee2d459581abc8ebdd2bb3783ba216f6c68872a50ecba9ab1

Tx prefix hash: 206bdd04556df4c352b090085e995a8d61baeb9382efe1dc8909bc812b85e0b7
Tx public key: e3a986dc33d47120ca2a9201a4397dc167d4a00dc494d666e27f25a2494ad5d0
Timestamp: 1704439933 Timestamp [UCT]: 2024-01-05 07:32:13 Age [y:d:h:m:s]: 01:333:01:16:12
Block: 928532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496906 RingCT/type: yes/0
Extra: 01e3a986dc33d47120ca2a9201a4397dc167d4a00dc494d666e27f25a2494ad5d00211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae2c2f21a377094bbdc5e976ad8d47477c4194251450efdf4dd0316b8139b486 0.600000000000 1386392 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": 928542, "vin": [ { "gen": { "height": 928532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae2c2f21a377094bbdc5e976ad8d47477c4194251450efdf4dd0316b8139b486" } } ], "extra": [ 1, 227, 169, 134, 220, 51, 212, 113, 32, 202, 42, 146, 1, 164, 57, 125, 193, 103, 212, 160, 13, 196, 148, 214, 102, 226, 127, 37, 162, 73, 74, 213, 208, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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