Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 684a71b745750d4c720b2606f3717c57e111ec1529129e2a14c77562f6955618

Tx prefix hash: 3885998934f1e55e62f61eea3b223c5a9a63ed1011884187ed0e3632ba112d8d
Tx public key: af8446f9a5c3f044ea2a4c0d3d0ddd0049c04cbd79ea73aeeaf9a8b60ef03acd
Timestamp: 1577912782 Timestamp [UCT]: 2020-01-01 21:06:22 Age [y:d:h:m:s]: 05:063:14:38:11
Block: 36619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195313 RingCT/type: yes/0
Extra: 01af8446f9a5c3f044ea2a4c0d3d0ddd0049c04cbd79ea73aeeaf9a8b60ef03acd021100000022d81c26c0000000000000000000

1 output(s) for total of 464.159137354000 dcy

stealth address amount amount idx
00: e6ac75b742d60d6ff3a10dced3c0105a7a3bba797bccffce236bbc5ba6ace162 464.159137354000 62065 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": 36629, "vin": [ { "gen": { "height": 36619 } } ], "vout": [ { "amount": 464159137354, "target": { "key": "e6ac75b742d60d6ff3a10dced3c0105a7a3bba797bccffce236bbc5ba6ace162" } } ], "extra": [ 1, 175, 132, 70, 249, 165, 195, 240, 68, 234, 42, 76, 13, 61, 13, 221, 0, 73, 192, 76, 189, 121, 234, 115, 174, 234, 249, 168, 182, 14, 240, 58, 205, 2, 17, 0, 0, 0, 34, 216, 28, 38, 192, 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