Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a2032d83056c0a05c4080b6b221a622c2fba33c199d73147be52dabff39ef17

Tx prefix hash: f3f0eeeaa6837dd917aa5f420134f3dd4f6ff388648f54f3d62492a8539ca3ed
Tx public key: e8548c1d6f705dfc767bddec73c1346eb0cbacf4a7f27b4830d4d09730d0148c
Timestamp: 1717930187 Timestamp [UCT]: 2024-06-09 10:49:47 Age [y:d:h:m:s]: 00:340:17:39:55
Block: 1040395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243525 RingCT/type: yes/0
Extra: 01e8548c1d6f705dfc767bddec73c1346eb0cbacf4a7f27b4830d4d09730d0148c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fa231af2093ee9dae77ced91c0e3a6f64b4cefa24b32806abf169330807d8d8 0.600000000000 1509052 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": 1040405, "vin": [ { "gen": { "height": 1040395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fa231af2093ee9dae77ced91c0e3a6f64b4cefa24b32806abf169330807d8d8" } } ], "extra": [ 1, 232, 84, 140, 29, 111, 112, 93, 252, 118, 123, 221, 236, 115, 193, 52, 110, 176, 203, 172, 244, 167, 242, 123, 72, 48, 212, 208, 151, 48, 208, 20, 140, 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