← previous blocknext block →recent activity
Analyzing
Block #98,533,158
17 transactions · 16 stateful · 2026-08-23 17:08:07 UTC
Parallelism
59/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,533,158 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w19w210w311w412w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc3baa205…f26e
0x34b655…2a6f
6 touches
3 conflicts
0xeb88ed4e…a342
0x34b655…2a6f
6 touches
3 conflicts
0xfe6eb5d0…7a62
0x34b655…2a6f
6 touches
3 conflicts
0x507a9f11…b4c4
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity