Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c493fe34b847d20579fb63d294daa7abb364e775045bb7c85fe09c5447ba620

Tx prefix hash: 9f108016fd03d9d6e074adae5cf96cee75f95075626b9fc485942c2d6761f180
Tx public key: 5a742ae85669c2b1e27d2a1495e1a0c0d11d236b9d278cb9f908cea9aa3722b5
Timestamp: 1641061913 Timestamp [UCT]: 2022-01-01 18:31:53 Age [y:d:h:m:s]: 03:005:13:39:20
Block: 408334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 783000 RingCT/type: yes/0
Extra: 015a742ae85669c2b1e27d2a1495e1a0c0d11d236b9d278cb9f908cea9aa3722b5021100000001edb0d4a3000000000000000000

1 output(s) for total of 27.229055123000 dcy

stealth address amount amount idx
00: cbc33344779953f23f4c411d1142ca1b3ff991c887c162d0aa851757da5778ab 27.229055123000 810321 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": 408344, "vin": [ { "gen": { "height": 408334 } } ], "vout": [ { "amount": 27229055123, "target": { "key": "cbc33344779953f23f4c411d1142ca1b3ff991c887c162d0aa851757da5778ab" } } ], "extra": [ 1, 90, 116, 42, 232, 86, 105, 194, 177, 226, 125, 42, 20, 149, 225, 160, 192, 209, 29, 35, 107, 157, 39, 140, 185, 249, 8, 206, 169, 170, 55, 34, 181, 2, 17, 0, 0, 0, 1, 237, 176, 212, 163, 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