← previous blocknext block →recent activity
Analyzing
Block #98,658,937
22 transactions · 22 stateful · 2026-08-24 04:03:41 UTC
Parallelism
82/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,658,937 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w16w07w19w010w111w213w314w115w016w117w220w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x801a6e57…d85c
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: Perpl
3 conflicts on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity