Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5439aed5c8be6066750377011eebd97d98f678040a64f8c5a23b2279b01b53c

Tx prefix hash: b2b6f1e52b8d44e515365d9a0f759591d7b488bce06b239fdb29e75926b32509
Tx public key: aa4e5a6edb6f161e5783b09f696b267d78578ba15c16d497515fd1b5b84df86c
Timestamp: 1747709811 Timestamp [UCT]: 2025-05-20 02:56:51 Age [y:d:h:m:s]: 00:258:01:34:48
Block: 1286749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182053 RingCT/type: yes/0
Extra: 01aa4e5a6edb6f161e5783b09f696b267d78578ba15c16d497515fd1b5b84df86c0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acaeb15301defa4db84e99d8fba8f0c9c16bf08e8da2aa2e26459e83d7e307fc 0.600000000000 1774216 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": 1286759, "vin": [ { "gen": { "height": 1286749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acaeb15301defa4db84e99d8fba8f0c9c16bf08e8da2aa2e26459e83d7e307fc" } } ], "extra": [ 1, 170, 78, 90, 110, 219, 111, 22, 30, 87, 131, 176, 159, 105, 107, 38, 125, 120, 87, 139, 161, 92, 22, 212, 151, 81, 95, 209, 181, 184, 77, 248, 108, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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