Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea4a1ab941f158dd45d3a06d4351bbff2a5b66ed1323b8a0b5836a47ee48428

Tx prefix hash: 2989f45f770992583f4de6b7c5e62146232d065bce4abd2b6035e484bf46ce83
Tx public key: 20451fd5637bb26a1459c0fead82b60a9159d527f7dc9d153e818dac98593580
Timestamp: 1704311841 Timestamp [UCT]: 2024-01-03 19:57:21 Age [y:d:h:m:s]: 01:317:03:23:32
Block: 927503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485483 RingCT/type: yes/0
Extra: 0120451fd5637bb26a1459c0fead82b60a9159d527f7dc9d153e818dac9859358002110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8405cb43f68c8191687db5594d48f24249604e89f3172a0c0e8d7e06818d54c 0.600000000000 1385339 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": 927513, "vin": [ { "gen": { "height": 927503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8405cb43f68c8191687db5594d48f24249604e89f3172a0c0e8d7e06818d54c" } } ], "extra": [ 1, 32, 69, 31, 213, 99, 123, 178, 106, 20, 89, 192, 254, 173, 130, 182, 10, 145, 89, 213, 39, 247, 220, 157, 21, 62, 129, 141, 172, 152, 89, 53, 128, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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