← previous blocknext block →recent activity
Analyzing
Block #98,078,813
25 transactions · 24 stateful · 2026-08-22 02:54:48 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,078,813 · 25 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
2w04w06w07w19w211w012w213w315w016w118w119w020w122w323w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xc6ff19c6…5250
0x34b655…2a6f
6 touches
3 conflicts
0x5fadfaca…5032
0x34b655…2a6f
6 touches
3 conflicts
0x7b6f910a…ccd2
0x34b655…2a6f
6 touches
3 conflicts
0x11db128b…1153
0x34b655…2a6f
4 touches
3 conflicts
0x62910921…3016
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity