Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ea20c2573dba18b0ee897f0bb680dc1e6a1d48bf06a776f563087366441e736

Tx prefix hash: df2655eaaaea7375f0655284ddceab40ae94ef74e97b1896a69278fd08299dd5
Tx public key: 00058ada5287b53d8e09cc705d6e4c73b8f5aa24525e6caa057ce4ab23ab0d64
Timestamp: 1697255072 Timestamp [UCT]: 2023-10-14 03:44:32 Age [y:d:h:m:s]: 01:249:18:51:34
Block: 869190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439457 RingCT/type: yes/0
Extra: 0100058ada5287b53d8e09cc705d6e4c73b8f5aa24525e6caa057ce4ab23ab0d6402110000000133af99f4000000000000000000

1 output(s) for total of 0.809119635000 dcy

stealth address amount amount idx
00: 09c2e9332c1a6d9a43654dc725daec9255c6419641eb7109ff6fa843e1b699fe 0.809119635000 1324025 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": 869200, "vin": [ { "gen": { "height": 869190 } } ], "vout": [ { "amount": 809119635, "target": { "key": "09c2e9332c1a6d9a43654dc725daec9255c6419641eb7109ff6fa843e1b699fe" } } ], "extra": [ 1, 0, 5, 138, 218, 82, 135, 181, 61, 142, 9, 204, 112, 93, 110, 76, 115, 184, 245, 170, 36, 82, 94, 108, 170, 5, 124, 228, 171, 35, 171, 13, 100, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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