Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a135ec48ef6d59151743943089650f7fa40aae5dbb4ceac86ac518a98a2dd7ca

Tx prefix hash: fb2dcacb34eee97764660108a2f0a03d5bc76cc14fef25629a54ece92537bdf5
Tx public key: 652c9dc1f2c8d0c8e4d9671f9236d48fcd3282a9f22a976ea7c3d776b33a63d5
Timestamp: 1707572999 Timestamp [UCT]: 2024-02-10 13:49:59 Age [y:d:h:m:s]: 01:044:02:45:05
Block: 954522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292566 RingCT/type: yes/0
Extra: 01652c9dc1f2c8d0c8e4d9671f9236d48fcd3282a9f22a976ea7c3d776b33a63d50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8554f2feca9e24fb4bb5aee4ee3c59c1986d41261da8bc24d2806bb34a00e179 0.600000000000 1413802 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": 954532, "vin": [ { "gen": { "height": 954522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8554f2feca9e24fb4bb5aee4ee3c59c1986d41261da8bc24d2806bb34a00e179" } } ], "extra": [ 1, 101, 44, 157, 193, 242, 200, 208, 200, 228, 217, 103, 31, 146, 54, 212, 143, 205, 50, 130, 169, 242, 42, 151, 110, 167, 195, 215, 118, 179, 58, 99, 213, 2, 17, 0, 0, 0, 2, 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