Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b3b6e4f11d816f0c1929934c963a137487a03551160b953043f8a620c5d1c6

Tx prefix hash: dcb36e37c28833b64bac42e3f158d25f5651afe249724d6cdf55a902b7988c19
Tx public key: 0fac8a65d49247d79dde5a2a1cd6e435129e3970c1d97fbff82328d2317229f1
Timestamp: 1638314080 Timestamp [UCT]: 2021-11-30 23:14:40 Age [y:d:h:m:s]: 03:028:14:44:11
Block: 385689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799357 RingCT/type: yes/0
Extra: 010fac8a65d49247d79dde5a2a1cd6e435129e3970c1d97fbff82328d2317229f1021100000029d6e4826b000000000000000000

1 output(s) for total of 32.363845783000 dcy

stealth address amount amount idx
00: 60aa6fb6d36dad07e102b2b81ab9993c3e92186865cffe195335e866fa8bf134 32.363845783000 778282 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": 385699, "vin": [ { "gen": { "height": 385689 } } ], "vout": [ { "amount": 32363845783, "target": { "key": "60aa6fb6d36dad07e102b2b81ab9993c3e92186865cffe195335e866fa8bf134" } } ], "extra": [ 1, 15, 172, 138, 101, 212, 146, 71, 215, 157, 222, 90, 42, 28, 214, 228, 53, 18, 158, 57, 112, 193, 217, 127, 191, 248, 35, 40, 210, 49, 114, 41, 241, 2, 17, 0, 0, 0, 41, 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