Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030e0853bfb1f4e577d923b6b79308612cf636a828104f12506179e200434c71

Tx prefix hash: fb95fd487640b781da14bb96429af2717308e034c8fde27a1389299773c4a899
Tx public key: 0feac4dcbbda1ee2afe3c3c15c9ef83da877c4939f27435fe0b8b1a7298ce1e5
Timestamp: 1697615666 Timestamp [UCT]: 2023-10-18 07:54:26 Age [y:d:h:m:s]: 01:099:15:41:31
Block: 872179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332431 RingCT/type: yes/0
Extra: 010feac4dcbbda1ee2afe3c3c15c9ef83da877c4939f27435fe0b8b1a7298ce1e5021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.790876987000 dcy

stealth address amount amount idx
00: 3f1a581692b31810e83df9d3ee5736752aad4a9c190b58b33ab9905983e7a401 0.790876987000 1327251 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": 872189, "vin": [ { "gen": { "height": 872179 } } ], "vout": [ { "amount": 790876987, "target": { "key": "3f1a581692b31810e83df9d3ee5736752aad4a9c190b58b33ab9905983e7a401" } } ], "extra": [ 1, 15, 234, 196, 220, 187, 218, 30, 226, 175, 227, 195, 193, 92, 158, 248, 61, 168, 119, 196, 147, 159, 39, 67, 95, 224, 184, 177, 167, 41, 140, 225, 229, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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