← previous blocknext block →recent activity
Analyzing
Block #98,508,058
11 transactions · 11 stateful · 2026-08-23 14:57:03 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,508,058 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb1747e2…f78b
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa771fb55…48d2
0x34b655…2a6f
4 touches
1 conflict
0x2cef1eff…9f14
0x34b655…2a6f
2 touches
0 conflicts
0x3055bfa7…ce68
0x34b655…2a6f
2 touches
0 conflicts
0x350d32fc…f659
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
6 conflicts on slot 0xbb1747e217…82f78b
Audit this contract →
← previous block·next block →recent activity