← previous blocknext block →recent activity
Analyzing
Block #98,388,148
6 transactions · 6 stateful · 2026-08-23 04:51:48 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,388,148 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02ae2bbb…b679
0x34b655…2a6f
4 touches
1 conflict
0xafc3a21b…d25a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x3522bbf4…54fb
0x34b655…2a6f
2 touches
0 conflicts
0x456ccc15…e999
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x67bf6242…5e74
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 0x02ae2bbb85…1bb679
Audit this contract →
← previous block·next block →recent activity