Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 328e8a041bb0004246145f81aae29f661f35c2cebd8437233183df3e5fb64320

Tx prefix hash: 1573c14b54700e8203931499b2b2a204f468887190507fe9586273fe3efd473a
Tx public key: 1a97ab3af5100e797e4edd388d2b739ac24cb49e721d7b176602b5026366f9c3
Timestamp: 1704090717 Timestamp [UCT]: 2024-01-01 06:31:57 Age [y:d:h:m:s]: 01:097:12:50:24
Block: 925650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330811 RingCT/type: yes/0
Extra: 011a97ab3af5100e797e4edd388d2b739ac24cb49e721d7b176602b5026366f9c30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dc955f7c19d6173e58c070eb8fa5beb41804654fbe7a9f1d5c5b08c493e394e 0.600000000000 1383414 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": 925660, "vin": [ { "gen": { "height": 925650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dc955f7c19d6173e58c070eb8fa5beb41804654fbe7a9f1d5c5b08c493e394e" } } ], "extra": [ 1, 26, 151, 171, 58, 245, 16, 14, 121, 126, 78, 221, 56, 141, 43, 115, 154, 194, 76, 180, 158, 114, 29, 123, 23, 102, 2, 181, 2, 99, 102, 249, 195, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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