Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464a986f514ff7158e5d9f858353849a88ba46ae0d427093fb6cb6ce24212069

Tx prefix hash: a567739e5cbf9aba164ba85cd4e97e6d45d7cef2be5f2f6112ae2a780a9fa6d5
Tx public key: 665b0ca301a4ac061eca365f81cab23729bcd7c04037d619f2dd5d6562bc6052
Timestamp: 1721665402 Timestamp [UCT]: 2024-07-22 16:23:22 Age [y:d:h:m:s]: 00:252:06:03:46
Block: 1071346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180213 RingCT/type: yes/0
Extra: 01665b0ca301a4ac061eca365f81cab23729bcd7c04037d619f2dd5d6562bc60520211000000015ff1157f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c6c55ca9935b5ad0d998401c7b1a3b97f5a357b36665015db3119978e25ea2d 0.600000000000 1543539 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": 1071356, "vin": [ { "gen": { "height": 1071346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c6c55ca9935b5ad0d998401c7b1a3b97f5a357b36665015db3119978e25ea2d" } } ], "extra": [ 1, 102, 91, 12, 163, 1, 164, 172, 6, 30, 202, 54, 95, 129, 202, 178, 55, 41, 188, 215, 192, 64, 55, 214, 25, 242, 221, 93, 101, 98, 188, 96, 82, 2, 17, 0, 0, 0, 1, 95, 241, 21, 127, 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