← previous blocknext block →recent activity
Analyzing
Block #98,366,928
33 transactions · 33 stateful · 2026-08-23 03:05:03 UTC
Parallelism
91/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,366,928 · 33 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
1w02w04w130w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x58fb4cd2…ef29
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x37c0660b…e0bf
0x34b655…2a6f
2 touches
0 conflicts
0x47e2a668…be99
0x34b655…2a6f
2 touches
0 conflicts
0x75f928fc…0465
0x34b655…2a6f
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity