← previous blocknext block →recent activity
Analyzing
Block #98,060,735
11 transactions · 11 stateful · 2026-08-22 01:23:49 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,060,735 · 11 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c5dc9f7…3729
0x34b655…2a6f
4 touches
1 conflict
0x49299fcf…c552
0x34b655…2a6f
4 touches
1 conflict
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0xd459bf7b…92c3
0x34b655…2a6f
4 touches
1 conflict
0x03bf49f6…3ec7
0x065c9d…c394
2 touches
0 conflicts
0x53b251d8…cbde
0x065c9d…c394
2 touches
0 conflicts
0xc26f0752…e293
0x065c9d…c394
2 touches
0 conflicts
0xe18822b5…8e43
0x065c9d…c394
2 touches
0 conflicts
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
1 conflict on slot 0x0c5dc9f747…533729
Audit this contract →
← previous block·next block →recent activity