Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d085ce157bf481861e0ba0f4fd57029ad7b89a2da447730a107e6935807e318

Tx prefix hash: 6d28d9261f6e55e3419ddd8084822eeaf911e4cd160ba8a394c58da14b00ef40
Tx public key: ef5c29ac5bc746a5f74bf32a50ca813c77961346e39108f066f19960b2c4259f
Timestamp: 1580615894 Timestamp [UCT]: 2020-02-02 03:58:14 Age [y:d:h:m:s]: 05:277:00:09:02
Block: 56830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1347708 RingCT/type: yes/0
Extra: 01ef5c29ac5bc746a5f74bf32a50ca813c77961346e39108f066f19960b2c4259f0211000000038a2ee0d9000000000000000000

1 output(s) for total of 397.831751415000 dcy

stealth address amount amount idx
00: f3182e265c6ce2e690f5b25be387d40ae1ab62a67b86621073d588e47634d93d 397.831751415000 104807 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": 56840, "vin": [ { "gen": { "height": 56830 } } ], "vout": [ { "amount": 397831751415, "target": { "key": "f3182e265c6ce2e690f5b25be387d40ae1ab62a67b86621073d588e47634d93d" } } ], "extra": [ 1, 239, 92, 41, 172, 91, 199, 70, 165, 247, 75, 243, 42, 80, 202, 129, 60, 119, 150, 19, 70, 227, 145, 8, 240, 102, 241, 153, 96, 178, 196, 37, 159, 2, 17, 0, 0, 0, 3, 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