Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f50d5b4b3966a0e3adaebe4b32cabc233355a172b87eb74bfef22eecfb875b00

Tx prefix hash: bd9916bde58087d00fef9f183a3850e58a3a012a79a7209c32692d56ca716528
Tx public key: 563acf83fc5024b4f75f9e957a7cd1fb01781f90b5d497d2234f95525f44c3de
Timestamp: 1729553131 Timestamp [UCT]: 2024-10-21 23:25:31 Age [y:d:h:m:s]: 01:020:05:53:59
Block: 1136714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272856 RingCT/type: yes/0
Extra: 01563acf83fc5024b4f75f9e957a7cd1fb01781f90b5d497d2234f95525f44c3de0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20c12a5ba85ffada977a385de3091d7488b90f9177dfdea662d23caa744ebcbc 0.600000000000 1620073 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": 1136724, "vin": [ { "gen": { "height": 1136714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20c12a5ba85ffada977a385de3091d7488b90f9177dfdea662d23caa744ebcbc" } } ], "extra": [ 1, 86, 58, 207, 131, 252, 80, 36, 180, 247, 95, 158, 149, 122, 124, 209, 251, 1, 120, 31, 144, 181, 212, 151, 210, 35, 79, 149, 82, 95, 68, 195, 222, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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