Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dab6ed8ce76c004f4128e6626043e85625e68a43e9e736cb7812c972d62b479

Tx prefix hash: c2e634f8e311c39383399c6bade8d15ed13c075278e3d9cf2e0cdd82a400a1c5
Tx public key: 9fcc69822e50e13671556e734cac68e81a60631a1d06e54045533e4d3d120392
Timestamp: 1707200541 Timestamp [UCT]: 2024-02-06 06:22:21 Age [y:d:h:m:s]: 01:278:10:56:10
Block: 951437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457784 RingCT/type: yes/0
Extra: 019fcc69822e50e13671556e734cac68e81a60631a1d06e54045533e4d3d1203920211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91f2e61a067f03b9bf9cf2f6bcd5458c06f389e7a485caa243379c9e1fabfc20 0.600000000000 1410201 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": 951447, "vin": [ { "gen": { "height": 951437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91f2e61a067f03b9bf9cf2f6bcd5458c06f389e7a485caa243379c9e1fabfc20" } } ], "extra": [ 1, 159, 204, 105, 130, 46, 80, 225, 54, 113, 85, 110, 115, 76, 172, 104, 232, 26, 96, 99, 26, 29, 6, 229, 64, 69, 83, 62, 77, 61, 18, 3, 146, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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