Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26cd2bf1c3d799388965252df4dbe7804d58c6cadc2d5e68cd0e2b5c696b784e

Tx prefix hash: ddf85258cbc28f6b388df64dd9c3a66ccdfd38bedf1ba89d17d7471871eb82c5
Tx public key: 77b8134631a591369e528b175789fdad32cc7e5c81388d79b4aea1029ec5f196
Timestamp: 1693032618 Timestamp [UCT]: 2023-08-26 06:50:18 Age [y:d:h:m:s]: 01:289:01:51:22
Block: 834154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467792 RingCT/type: yes/0
Extra: 0177b8134631a591369e528b175789fdad32cc7e5c81388d79b4aea1029ec5f19602110000000d75e3f0e9000000000000000000

1 output(s) for total of 1.057064783000 dcy

stealth address amount amount idx
00: 202e62d1d5c80daef588cd95313f1f45ddd47be5299dbb7ce5689206be95d83b 1.057064783000 1286640 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": 834164, "vin": [ { "gen": { "height": 834154 } } ], "vout": [ { "amount": 1057064783, "target": { "key": "202e62d1d5c80daef588cd95313f1f45ddd47be5299dbb7ce5689206be95d83b" } } ], "extra": [ 1, 119, 184, 19, 70, 49, 165, 145, 54, 158, 82, 139, 23, 87, 137, 253, 173, 50, 204, 126, 92, 129, 56, 141, 121, 180, 174, 161, 2, 158, 197, 241, 150, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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