← previous blocknext block →recent activity
Analyzing
Block #99,317,644
16 transactions · 16 stateful · 2026-08-26 11:31:30 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,317,644 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w110w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc908778…2ce2
0x8964d7…10f8
4 touches
1 conflict
0xfc908778…2cdd
0x8964d7…10f8
4 touches
1 conflict
0xfc908778…2ce0
0x8964d7…10f8
4 touches
1 conflict
0xfc908778…2ce1
0x8964d7…10f8
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0xb0f5d668…99ac
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x8964d7c9…5b10f8
1 conflict on slot 0xfc90877801…972ce2
Audit this contract →
← previous block·next block →recent activity