Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9887b6ca73eeb6f3f21da3b749477c46ad874b97930f2f081601215193c5fdff

Tx prefix hash: 1cda1337bdf50be38e55a2fb25ac1e9b28b0f4318106d173a9290e7aa43b9772
Tx public key: 965c37bc537227bdcc61da375d7f1e98bd4185a7da4e2e145a692c4fbe093a51
Timestamp: 1733521771 Timestamp [UCT]: 2024-12-06 21:49:31 Age [y:d:h:m:s]: 00:116:05:18:14
Block: 1169553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82846 RingCT/type: yes/0
Extra: 01965c37bc537227bdcc61da375d7f1e98bd4185a7da4e2e145a692c4fbe093a51021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c737f08e82a51354efaf328bfd41213d9b24b5eb8a649d14915a5dbbd6a264c 0.600000000000 1655272 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": 1169563, "vin": [ { "gen": { "height": 1169553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c737f08e82a51354efaf328bfd41213d9b24b5eb8a649d14915a5dbbd6a264c" } } ], "extra": [ 1, 150, 92, 55, 188, 83, 114, 39, 189, 204, 97, 218, 55, 93, 127, 30, 152, 189, 65, 133, 167, 218, 78, 46, 20, 90, 105, 44, 79, 190, 9, 58, 81, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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