← previous blocknext block →recent activity
Analyzing
Block #99,456,982
19 transactions · 19 stateful · 2026-08-26 23:13:07 UTC
Parallelism
84/100
Blocked
16%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,456,982 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w216w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e8a6177…499b
0x34b655…2a6f
6 touches
3 conflicts
0xd6a6d752…518f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9536b6cb…74bb
0x34b655…2a6f
4 touches
1 conflict
0x5ab3fb12…8e76
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
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
3 conflicts on slot 0x8e8a617749…fc499b
Audit this contract →
← previous block·next block →recent activity