← previous blocknext block →recent activity
Analyzing
Block #100,029,088
52 transactions · 40 stateful · 2026-08-28 23:26:49 UTC
Parallelism
87/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,029,088 · 52 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w28w314w016w418w119w220w321w531w634w451w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xc04f72f2…8af7
0xd32edf…ff58
11 touches
15 conflicts
0x15698ac9…2a46
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0x06e40499…165e
0x2b46c0…1669
6 touches
3 conflicts
0x5138188e…796b
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity