Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f53ac7e58f2269d7d2caf98fbb595d2d493a81b5877bafeadca6e61735f642

Tx prefix hash: e107524e7677bc67340bf8ed775d0cada760bafe23913dded0fa4b199ad7778d
Tx public key: aa6f63bbcc6c62bbb253c4b36fb59e8735362825d0e031e0506b8c0ccbc9409f
Timestamp: 1724693540 Timestamp [UCT]: 2024-08-26 17:32:20 Age [y:d:h:m:s]: 00:234:12:25:48
Block: 1096454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167492 RingCT/type: yes/0
Extra: 01aa6f63bbcc6c62bbb253c4b36fb59e8735362825d0e031e0506b8c0ccbc9409f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca815671ebed0b63eea9b0a64858a89f5a30b213f48eeb37a985612b4c7973a0 0.600000000000 1571643 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": 1096464, "vin": [ { "gen": { "height": 1096454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca815671ebed0b63eea9b0a64858a89f5a30b213f48eeb37a985612b4c7973a0" } } ], "extra": [ 1, 170, 111, 99, 187, 204, 108, 98, 187, 178, 83, 196, 179, 111, 181, 158, 135, 53, 54, 40, 37, 208, 224, 49, 224, 80, 107, 140, 12, 203, 201, 64, 159, 2, 17, 0, 0, 0, 4, 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