Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44b65f897126002be3b7cb9f4c80afb7e48d9c80ebc0eda4c7e2acba12d6ece6

Tx prefix hash: e00832adec34a3f5a04ba2ddea090453463880fca944b277e78172545fb9c83d
Tx public key: f9b6e969b3b0080c0f4ace47b3e76d3ffab8834fc78158211a50d3bee1f00309
Timestamp: 1737903561 Timestamp [UCT]: 2025-01-26 14:59:21 Age [y:d:h:m:s]: 00:148:06:22:08
Block: 1205781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105579 RingCT/type: yes/0
Extra: 01f9b6e969b3b0080c0f4ace47b3e76d3ffab8834fc78158211a50d3bee1f00309021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68e49409c59bd157f0efa4a72ebefeab4d5c29ed6860e1b252bf177f9cee3569 0.600000000000 1692480 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": 1205791, "vin": [ { "gen": { "height": 1205781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68e49409c59bd157f0efa4a72ebefeab4d5c29ed6860e1b252bf177f9cee3569" } } ], "extra": [ 1, 249, 182, 233, 105, 179, 176, 8, 12, 15, 74, 206, 71, 179, 231, 109, 63, 250, 184, 131, 79, 199, 129, 88, 33, 26, 80, 211, 190, 225, 240, 3, 9, 2, 17, 0, 0, 0, 7, 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