Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f4bffaee238c016c55c2036f60c34b263692bf0d0f17d0c763e49e7f805e8e0

Tx prefix hash: 05f66b493df5ba71fa09f89b37bd919f8a10b7c08aba12b8026e7af1be2320ce
Tx public key: 176dcc380f238f01a55f9d37307082065fba7529ce2876d3abc8aa723ccc5766
Timestamp: 1726780609 Timestamp [UCT]: 2024-09-19 21:16:49 Age [y:d:h:m:s]: 00:177:02:04:27
Block: 1113775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126399 RingCT/type: yes/0
Extra: 01176dcc380f238f01a55f9d37307082065fba7529ce2876d3abc8aa723ccc5766021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 395cc8a8a40c8cd95bcaaf27b5f10ec67131b5cb73b6e989e8e126297ef9231a 0.600000000000 1593572 of 15

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": 1113785, "vin": [ { "gen": { "height": 1113775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "395cc8a8a40c8cd95bcaaf27b5f10ec67131b5cb73b6e989e8e126297ef9231a" } } ], "extra": [ 1, 23, 109, 204, 56, 15, 35, 143, 1, 165, 95, 157, 55, 48, 112, 130, 6, 95, 186, 117, 41, 206, 40, 118, 211, 171, 200, 170, 114, 60, 204, 87, 102, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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