Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b386ee1b50c081be9ecbf8f7a13c8278a7db94c7a6cbdd2a439346e4405ba4c

Tx prefix hash: 11d8374b4c8cca65aa644a2c0cd37e9de0588e774b3d5bfc8b8f7a60898e671a
Tx public key: 80fc694b9622cab87dff2902491ae8a21050bdfcbec734abb8d28c78eeba491a
Timestamp: 1696119207 Timestamp [UCT]: 2023-10-01 00:13:27 Age [y:d:h:m:s]: 01:228:16:27:30
Block: 859778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424506 RingCT/type: yes/0
Extra: 0180fc694b9622cab87dff2902491ae8a21050bdfcbec734abb8d28c78eeba491a0211000000154b8f5122000000000000000000

1 output(s) for total of 0.869357925000 dcy

stealth address amount amount idx
00: 64a9a0e37530f52a5ecebeb3155ff123852de3f83ae11affb7bd4d1dca8e8499 0.869357925000 1314024 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": 859788, "vin": [ { "gen": { "height": 859778 } } ], "vout": [ { "amount": 869357925, "target": { "key": "64a9a0e37530f52a5ecebeb3155ff123852de3f83ae11affb7bd4d1dca8e8499" } } ], "extra": [ 1, 128, 252, 105, 75, 150, 34, 202, 184, 125, 255, 41, 2, 73, 26, 232, 162, 16, 80, 189, 252, 190, 199, 52, 171, 184, 210, 140, 120, 238, 186, 73, 26, 2, 17, 0, 0, 0, 21, 75, 143, 81, 34, 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