← previous blocknext block →recent activity
Analyzing
Block #99,934,341
28 transactions · 27 stateful · 2026-08-28 15:29:35 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,934,341 · 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
2w04w16w07w110w013w214w320w023w125w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0f5d668…99ac
0x34b655…2a6f
8 touches
6 conflicts
0xbd590df7…9891
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0x49d6800f…40eb
0x34b655…2a6f
6 touches
3 conflicts
0xa66499c2…9f47
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 0xb0f5d66855…1a99ac
Audit this contract →
← previous block·next block →recent activity