Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1aea12d230974de9e0d8aa8537729f2ca56c20e9e8e6ea8a754e8b67b8192b16

Tx prefix hash: f425d8cfd232b998705d92fbf2336790e3bc39f7f57e7f51484d1e8338e440a8
Tx public key: 80ffbab4828463237d737636efadfac1a5181de097d9b0adfa5cc850977c1f5f
Timestamp: 1577789740 Timestamp [UCT]: 2019-12-31 10:55:40 Age [y:d:h:m:s]: 05:306:15:13:39
Block: 35657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366681 RingCT/type: yes/0
Extra: 0180ffbab4828463237d737636efadfac1a5181de097d9b0adfa5cc850977c1f5f0211000000104943cd9f000000000000000000

1 output(s) for total of 467.578368296000 dcy

stealth address amount amount idx
00: ad6ccbcacbe4023c6df9dbd0af629ef4e520eb6f2991b2bd8d65475c9ec784d9 467.578368296000 60176 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": 35667, "vin": [ { "gen": { "height": 35657 } } ], "vout": [ { "amount": 467578368296, "target": { "key": "ad6ccbcacbe4023c6df9dbd0af629ef4e520eb6f2991b2bd8d65475c9ec784d9" } } ], "extra": [ 1, 128, 255, 186, 180, 130, 132, 99, 35, 125, 115, 118, 54, 239, 173, 250, 193, 165, 24, 29, 224, 151, 217, 176, 173, 250, 92, 200, 80, 151, 124, 31, 95, 2, 17, 0, 0, 0, 16, 73, 67, 205, 159, 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