Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f44a0e2d62f9f425212f2d51f0b8941ea53fc0a5c28791fa932f74d476496c

Tx prefix hash: 41ce036bc58a5bf746ce019ab38c6e83f470b3dc856c8b926df45c774c0646bd
Tx public key: aaf5084f1b4498a8483da65e6ce1394653079056e3407ca18654bbcfd338455f
Timestamp: 1721284896 Timestamp [UCT]: 2024-07-18 06:41:36 Age [y:d:h:m:s]: 01:121:15:32:38
Block: 1068215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345454 RingCT/type: yes/0
Extra: 01aaf5084f1b4498a8483da65e6ce1394653079056e3407ca18654bbcfd338455f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de253330b7ec1251e273da7b0f46d4f83e94c9c35f265223e9daa51cee3464f1 0.600000000000 1539280 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": 1068225, "vin": [ { "gen": { "height": 1068215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de253330b7ec1251e273da7b0f46d4f83e94c9c35f265223e9daa51cee3464f1" } } ], "extra": [ 1, 170, 245, 8, 79, 27, 68, 152, 168, 72, 61, 166, 94, 108, 225, 57, 70, 83, 7, 144, 86, 227, 64, 124, 161, 134, 84, 187, 207, 211, 56, 69, 95, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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