Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d59fa787830d668e7873241080aa07911ca0720663fa7e96728f08a9b68819f1

Tx prefix hash: bf859840eeb3a66e90cd33f995ba8797e9a0c45593d9f640b8d16e8b3bd374b9
Tx public key: d7e0d7dbd637cb5f7f2f67a08bf0281893a28af3ac252592f8c229f76c00f0ae
Timestamp: 1579149553 Timestamp [UCT]: 2020-01-16 04:39:13 Age [y:d:h:m:s]: 04:294:21:50:20
Block: 46540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100244 RingCT/type: yes/0
Extra: 01d7e0d7dbd637cb5f7f2f67a08bf0281893a28af3ac252592f8c229f76c00f0ae0211000000108a2ee0d9000000000000000000

1 output(s) for total of 430.330369961000 dcy

stealth address amount amount idx
00: 1c7b7d2e31c85faab02d574e3958b13c1d6640f32821bd8598f4606f620cbf8f 430.330369961000 85658 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": 46550, "vin": [ { "gen": { "height": 46540 } } ], "vout": [ { "amount": 430330369961, "target": { "key": "1c7b7d2e31c85faab02d574e3958b13c1d6640f32821bd8598f4606f620cbf8f" } } ], "extra": [ 1, 215, 224, 215, 219, 214, 55, 203, 95, 127, 47, 103, 160, 139, 240, 40, 24, 147, 162, 138, 243, 172, 37, 37, 146, 248, 194, 41, 247, 108, 0, 240, 174, 2, 17, 0, 0, 0, 16, 138, 46, 224, 217, 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