Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a5bc7fe1af23bcadef7d39cbb5b5e962b3b12e4a72910af240fcf99f112ee8

Tx prefix hash: 4c14df0252a642a0036a27d73f97daf2a9857c39774a65dc9cc7cba7e0c3decf
Tx public key: a6057352f749615a911c52d1698dff1a9fd451b18cef0269570dae2ee1cbc5b2
Timestamp: 1696409179 Timestamp [UCT]: 2023-10-04 08:46:19 Age [y:d:h:m:s]: 01:190:08:36:42
Block: 862172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397100 RingCT/type: yes/0
Extra: 01a6057352f749615a911c52d1698dff1a9fd451b18cef0269570dae2ee1cbc5b2021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.853623373000 dcy

stealth address amount amount idx
00: c44d4b34a4e5f3d2c177fddf0a1ce58a917658043f867c412b0fd53c7bfa078e 0.853623373000 1316574 of 0

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": 862182, "vin": [ { "gen": { "height": 862172 } } ], "vout": [ { "amount": 853623373, "target": { "key": "c44d4b34a4e5f3d2c177fddf0a1ce58a917658043f867c412b0fd53c7bfa078e" } } ], "extra": [ 1, 166, 5, 115, 82, 247, 73, 97, 90, 145, 28, 82, 209, 105, 141, 255, 26, 159, 212, 81, 177, 140, 239, 2, 105, 87, 13, 174, 46, 225, 203, 197, 178, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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