Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19f0fcf8b41c0afd29988d4b2a8ac4b1cc713db74db3f9b48177d5eb771bbe3d

Tx prefix hash: 11c55bc122981f3e4de9dcaf8c839c624a7ec0175e75b1dacece2c372522ccb4
Tx public key: 1b2aafaa1a0137a65913ea5f0bf48efb4eaae09ef3203b4928c5666ce8384d86
Timestamp: 1712313664 Timestamp [UCT]: 2024-04-05 10:41:04 Age [y:d:h:m:s]: 01:001:16:24:48
Block: 993806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262164 RingCT/type: yes/0
Extra: 011b2aafaa1a0137a65913ea5f0bf48efb4eaae09ef3203b4928c5666ce8384d8602110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1069d66366fce64b7f5f1fc5b8cd11a0ccb7818a6c04a6d876d15ff8b04d396 0.600000000000 1454194 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": 993816, "vin": [ { "gen": { "height": 993806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1069d66366fce64b7f5f1fc5b8cd11a0ccb7818a6c04a6d876d15ff8b04d396" } } ], "extra": [ 1, 27, 42, 175, 170, 26, 1, 55, 166, 89, 19, 234, 95, 11, 244, 142, 251, 78, 170, 224, 158, 243, 32, 59, 73, 40, 197, 102, 108, 232, 56, 77, 134, 2, 17, 0, 0, 0, 7, 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