Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a799cb38eb416e667c65b615e23d9a39e859d50cdc5d16e43e4bcf0db7f89748

Tx prefix hash: 99205ee991ea5706da4202d5acbad0a1b4a66afe2472aa8055f46769c000f143
Tx public key: 5c1b8493c0dc9e3fa72c09f3241994bc29419aadad88131e82f1d079875af8f8
Timestamp: 1729821110 Timestamp [UCT]: 2024-10-25 01:51:50 Age [y:d:h:m:s]: 00:089:17:28:23
Block: 1138945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64105 RingCT/type: yes/0
Extra: 015c1b8493c0dc9e3fa72c09f3241994bc29419aadad88131e82f1d079875af8f8021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97f93033ea2502ce9f2ef25f78846bc8b6e86f9860abf5289a4e618366464cdf 0.600000000000 1622688 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": 1138955, "vin": [ { "gen": { "height": 1138945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97f93033ea2502ce9f2ef25f78846bc8b6e86f9860abf5289a4e618366464cdf" } } ], "extra": [ 1, 92, 27, 132, 147, 192, 220, 158, 63, 167, 44, 9, 243, 36, 25, 148, 188, 41, 65, 154, 173, 173, 136, 19, 30, 130, 241, 208, 121, 135, 90, 248, 248, 2, 17, 0, 0, 0, 8, 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