Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fee283a8ada67ba493f0fbbcc6835d89de3476f3bd15764b7df38b22b9905855

Tx prefix hash: 3b79399cb29cca7ef4add11cc76bdeb36f48ab3a9fd8d33b2eb02100844b1898
Tx public key: 1d82359564b90fd9b4b60cc2ed2ebc6cdfe8940ff681b26c27e8f2e4905b9ad1
Timestamp: 1656352816 Timestamp [UCT]: 2022-06-27 18:00:16 Age [y:d:h:m:s]: 02:151:19:39:26
Block: 531630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 629809 RingCT/type: yes/0
Extra: 011d82359564b90fd9b4b60cc2ed2ebc6cdfe8940ff681b26c27e8f2e4905b9ad10211000000192e6b1fd5000000000000000000

1 output(s) for total of 10.629343446000 dcy

stealth address amount amount idx
00: 2b1b0f6eacb6ed7d89398a6f2b068446ccb02b7f9e67a1b9e31708b1514b35a0 10.629343446000 960801 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": 531640, "vin": [ { "gen": { "height": 531630 } } ], "vout": [ { "amount": 10629343446, "target": { "key": "2b1b0f6eacb6ed7d89398a6f2b068446ccb02b7f9e67a1b9e31708b1514b35a0" } } ], "extra": [ 1, 29, 130, 53, 149, 100, 185, 15, 217, 180, 182, 12, 194, 237, 46, 188, 108, 223, 232, 148, 15, 246, 129, 178, 108, 39, 232, 242, 228, 144, 91, 154, 209, 2, 17, 0, 0, 0, 25, 46, 107, 31, 213, 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