← previous blocknext block →recent activity
Analyzing
Block #100,616,229
24 transactions · 20 stateful · 2026-08-31 00:45:20 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,616,229 · 24 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
1w02w16w18w09w111w012w113w214w315w221w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x282c7bf6…f709
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8db32935…81a7
0x34b655…2a6f
6 touches
3 conflicts
0x617d82b7…0806
0xd32edf…ff58
5 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
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
3 conflicts on slot 0x282c7bf66a…1cf709
Audit this contract →
← previous block·next block →recent activity