← previous blocknext block →recent activity
Analyzing
Block #99,184,260
28 transactions · 22 stateful · 2026-08-26 00:20:22 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,184,260 · 28 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
1w02w03w04w17w08w19w121w123w224w125w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1fb6e47f…b99a
0x34b655…2a6f
4 touches
1 conflict
0x587cd094…a294
0x34b655…2a6f
4 touches
1 conflict
0xe10ff4f0…94b7
0x99c7a7…8bf0
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x0449d018…e334
0x754704…b603
4 touches
1 conflict
0xe332b0a5…0bdb
0x754704…b603
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 0x631b41138f…31baa9
Audit this contract →
← previous block·next block →recent activity