Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1933c90e64d181ad6e8e037aaf6204e71739507646a7bbf9143eda57aef7ba9a

Tx prefix hash: f628f036ac7185c8a758729e0a2f8de94c66b5c998a0b47a35e75bd0269fc290
Tx public key: ec64625d12d6e84f003ec6aed56388f3923cd2d9fb0a8fd3b3a28cb4417c1a26
Timestamp: 1708292081 Timestamp [UCT]: 2024-02-18 21:34:41 Age [y:d:h:m:s]: 00:269:21:32:52
Block: 960498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193237 RingCT/type: yes/0
Extra: 01ec64625d12d6e84f003ec6aed56388f3923cd2d9fb0a8fd3b3a28cb4417c1a260211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd5b33210430af8c495ccf64551c2161f0bda2f4fa9d20fcf435489aceb679f1 0.600000000000 1420069 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": 960508, "vin": [ { "gen": { "height": 960498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd5b33210430af8c495ccf64551c2161f0bda2f4fa9d20fcf435489aceb679f1" } } ], "extra": [ 1, 236, 100, 98, 93, 18, 214, 232, 79, 0, 62, 198, 174, 213, 99, 136, 243, 146, 60, 210, 217, 251, 10, 143, 211, 179, 162, 140, 180, 65, 124, 26, 38, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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