← previous blocknext block →recent activity
Analyzing
Block #98,217,508
17 transactions · 16 stateful · 2026-08-22 14:33:19 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,217,508 · 17 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
2w05w07w010w114w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x386d08f4…5a01
0x34b655…2a6f
4 touches
1 conflict
0x61ca6437…2142
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
2 touches
0 conflicts
0x5e072bcf…6b9f
0x34b655…2a6f
2 touches
0 conflicts
0x5e6748a8…60a9
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 0x386d08f44a…fc5a01
Audit this contract →
← previous block·next block →recent activity