← previous blocknext block →recent activity
Analyzing
Block #100,627,292
30 transactions · 29 stateful · 2026-08-31 01:40:59 UTC
Parallelism
77/100
Blocked
24%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,627,292 · 30 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
5w06w19w012w113w214w317w418w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x5684aadd…8d62
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xead15497…1dbe
0x34b655…2a6f
4 touches
1 conflict
0x07b538eb…09f8
0x34b655…2a6f
4 touches
1 conflict
0x16ebf93b…ce00
0x34b655…2a6f
4 touches
1 conflict
0x17d0feef…8f30
0x34b655…2a6f
4 touches
1 conflict
0x35012b34…4843
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity