← previous blocknext block →recent activity
Analyzing
Block #98,643,208
17 transactions · 17 stateful · 2026-08-24 02:41:36 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,643,208 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w012w113w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5dc4e6c5…9491
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x5dc4e6c5…948c
0x8964d7…10f8
6 touches
3 conflicts
0x5dc4e6c5…948d
0x8964d7…10f8
6 touches
3 conflicts
0x5dc4e6c5…9490
0x8964d7…10f8
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
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
3 conflicts on slot 0x5dc4e6c575…a29491
Audit this contract →
← previous block·next block →recent activity