← previous blocknext block →recent activity
Analyzing
Block #98,388,564
18 transactions · 16 stateful · 2026-08-23 04:53:54 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,388,564 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w210w111w012w213w315w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58799a46…7030
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x94789504…4525
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x58799a469e…b57030
Audit this contract →
← previous block·next block →recent activity