Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8e33e87985aa63f85cb9357a065f173b965c4e6adfeabcc5667bd94c498d00b

Tx prefix hash: 476363ff856468452e8650dce6ddbca97d2e60c0a3c3314edf7d0d8261322e68
Tx public key: f03b72eb8a6a9d70ae4927fdc023efbe3a205f25a83103240c38ff8048275e27
Timestamp: 1735468885 Timestamp [UCT]: 2024-12-29 10:41:25 Age [y:d:h:m:s]: 00:172:21:07:31
Block: 1185660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123245 RingCT/type: yes/0
Extra: 01f03b72eb8a6a9d70ae4927fdc023efbe3a205f25a83103240c38ff8048275e27021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a4a587bf5ed52f6815c2d8b910c917496e37c4bd372260089590b01659a6a6 0.600000000000 1672135 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": 1185670, "vin": [ { "gen": { "height": 1185660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a4a587bf5ed52f6815c2d8b910c917496e37c4bd372260089590b01659a6a6" } } ], "extra": [ 1, 240, 59, 114, 235, 138, 106, 157, 112, 174, 73, 39, 253, 192, 35, 239, 190, 58, 32, 95, 37, 168, 49, 3, 36, 12, 56, 255, 128, 72, 39, 94, 39, 2, 17, 0, 0, 0, 3, 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