← previous blocknext block →recent activity
Analyzing
Block #98,386,831
44 transactions · 43 stateful · 2026-08-23 04:45:11 UTC
Parallelism
93/100
Blocked
9%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,386,831 · 44 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
1w02w17w08w037w138w242w043w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6264bbd…cf0b
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0b4267f7…96c0
0x34b655…2a6f
4 touches
1 conflict
0x13938a09…5f88
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 0xb6264bbd6d…94cf0b
Audit this contract →
← previous block·next block →recent activity