Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d82b0a6fe676614df64f3487655f94a5cf943f24b75b3a29746e1e9b387ddd81

Tx prefix hash: 5ddf2acc9ab252d350f97bbadbeedd880a9070479bab8b07806c98722bbe6ee6
Tx public key: 1ae4702a1c73ed57456cee55542d531d8521b3f07da13b1b1a4e77224ea1b1c1
Timestamp: 1734094739 Timestamp [UCT]: 2024-12-13 12:58:59 Age [y:d:h:m:s]: 00:110:09:03:37
Block: 1174323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78646 RingCT/type: yes/0
Extra: 011ae4702a1c73ed57456cee55542d531d8521b3f07da13b1b1a4e77224ea1b1c1021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 656b5b5e09d5a4479c832e2cd9e3011570350b3fa007bdaa0cf82978a989a460 0.600000000000 1660460 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": 1174333, "vin": [ { "gen": { "height": 1174323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "656b5b5e09d5a4479c832e2cd9e3011570350b3fa007bdaa0cf82978a989a460" } } ], "extra": [ 1, 26, 228, 112, 42, 28, 115, 237, 87, 69, 108, 238, 85, 84, 45, 83, 29, 133, 33, 179, 240, 125, 161, 59, 27, 26, 78, 119, 34, 78, 161, 177, 193, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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