← previous blocknext block →recent activity
Analyzing
Block #98,606,125
13 transactions · 12 stateful · 2026-08-23 23:28:42 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,606,125 · 13 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
1w05w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x5e1822f4…c400
0x34b655…2a6f
4 touches
1 conflict
0xf2410d5d…8153
0x34b655…2a6f
4 touches
1 conflict
0x2924fbfa…b72b
0x34b655…2a6f
2 touches
0 conflicts
0x3040889b…532b
0x34b655…2a6f
2 touches
0 conflicts
0x98834cc0…6c23
0x34b655…2a6f
2 touches
0 conflicts
0xb8d2c781…218d
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 0xe4af4c87c3…c59964
Audit this contract →
← previous block·next block →recent activity