← previous blocknext block →recent activity
Analyzing
Block #98,745,340
22 transactions · 15 stateful · 2026-08-24 11:25:05 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,745,340 · 22 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
5w06w011w012w114w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb482658a…e4f5
0x34b655…2a6f
4 touches
1 conflict
0xb88a78e9…02ee
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf984d8ab…6e4f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x9d120070…8aff
0x57ea24…2cec
2 touches
0 conflicts
0xe60cff44…1b50
0x57ea24…2cec
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 0xb482658a15…f3e4f5
Audit this contract →
← previous block·next block →recent activity