Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06d76d246337eb1ceab0d551b697ff5ff8dc45b91e819d78413ad974dc1e0a52

Tx prefix hash: b415515ba29a5c5bd9bf857f762b1d66a2a2111df047baec397a299d48e017df
Tx public key: 32db9f451de9d5cb4b89e952eb87a8ecc371bcca7dd6fba25b7cd8c69851b190
Timestamp: 1752085328 Timestamp [UCT]: 2025-07-09 18:22:08 Age [y:d:h:m:s]: 00:127:10:23:50
Block: 1322092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89620 RingCT/type: yes/0
Extra: 0132db9f451de9d5cb4b89e952eb87a8ecc371bcca7dd6fba25b7cd8c69851b1900211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e92b130c59205f4299ad1a4cb9e7c11204280a5bf92c62563ce932afdb11b454 0.600000000000 1809805 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": 1322102, "vin": [ { "gen": { "height": 1322092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e92b130c59205f4299ad1a4cb9e7c11204280a5bf92c62563ce932afdb11b454" } } ], "extra": [ 1, 50, 219, 159, 69, 29, 233, 213, 203, 75, 137, 233, 82, 235, 135, 168, 236, 195, 113, 188, 202, 125, 214, 251, 162, 91, 124, 216, 198, 152, 81, 177, 144, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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