Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6172ecfdc9a8af2b35ff24445af91d89b9c8ddd7769dd60c9b52cdd3192d7a81

Tx prefix hash: e1806b9a647b292eac410467684279741e2e9b989596af64b986868369b5ad4f
Tx public key: 8ae4139a2756adcabd562f79ce7c87bb8cb8aee9f11bfa2ea37905c894353feb
Timestamp: 1711296419 Timestamp [UCT]: 2024-03-24 16:06:59 Age [y:d:h:m:s]: 01:016:20:27:48
Block: 985418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273003 RingCT/type: yes/0
Extra: 018ae4139a2756adcabd562f79ce7c87bb8cb8aee9f11bfa2ea37905c894353feb0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f11814af5b22f1023ced066914fa8238b60bcd7bbbc64143a10b646c1444e59d 0.600000000000 1445629 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": 985428, "vin": [ { "gen": { "height": 985418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f11814af5b22f1023ced066914fa8238b60bcd7bbbc64143a10b646c1444e59d" } } ], "extra": [ 1, 138, 228, 19, 154, 39, 86, 173, 202, 189, 86, 47, 121, 206, 124, 135, 187, 140, 184, 174, 233, 241, 27, 250, 46, 163, 121, 5, 200, 148, 53, 63, 235, 2, 17, 0, 0, 0, 4, 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