Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63f90703fa8c2426c8bc18337c4cafc2d1f66eed9c48809a2f9c7efe12933d8f

Tx prefix hash: b9c332db805a1bc2bf7ca4664fd667b3a1e6c8841ff920b89f334e0311873b69
Tx public key: b7981c488c4cd9566a8ddde7a1d567088bb6388740ab62ad5aaecebfee219c46
Timestamp: 1712733180 Timestamp [UCT]: 2024-04-10 07:13:00 Age [y:d:h:m:s]: 01:255:23:29:26
Block: 997289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441679 RingCT/type: yes/0
Extra: 01b7981c488c4cd9566a8ddde7a1d567088bb6388740ab62ad5aaecebfee219c46021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb94cb6d040439059c37716b0eb9d73312f8d1e28aebf04ddaf897778d3ae426 0.600000000000 1457719 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": 997299, "vin": [ { "gen": { "height": 997289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb94cb6d040439059c37716b0eb9d73312f8d1e28aebf04ddaf897778d3ae426" } } ], "extra": [ 1, 183, 152, 28, 72, 140, 76, 217, 86, 106, 141, 221, 231, 161, 213, 103, 8, 139, 182, 56, 135, 64, 171, 98, 173, 90, 174, 206, 191, 238, 33, 156, 70, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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