Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f63815cb89503d694d56cfed8b53e3d0ead3fffd06932bd5c5e553d024bf1887

Tx prefix hash: 0e5b9620b1fedc384ce70e0dae6cee2ba4eb132e959298b85c2c52fe28e583ca
Tx public key: f12d473846f10d52f650e54ab144fffcc783c7b0bd0fa479e12c3a52abf58b5b
Timestamp: 1708974973 Timestamp [UCT]: 2024-02-26 19:16:13 Age [y:d:h:m:s]: 01:093:13:19:07
Block: 966159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327918 RingCT/type: yes/0
Extra: 01f12d473846f10d52f650e54ab144fffcc783c7b0bd0fa479e12c3a52abf58b5b02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c700555c2f3a81131f29df531b98af972829af32dc0b885825f95de5919f78f 0.600000000000 1425916 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": 966169, "vin": [ { "gen": { "height": 966159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c700555c2f3a81131f29df531b98af972829af32dc0b885825f95de5919f78f" } } ], "extra": [ 1, 241, 45, 71, 56, 70, 241, 13, 82, 246, 80, 229, 74, 177, 68, 255, 252, 199, 131, 199, 176, 189, 15, 164, 121, 225, 44, 58, 82, 171, 245, 139, 91, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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