← previous blocknext block →recent activity
Analyzing
Block #100,850,601
23 transactions · 22 stateful · 2026-08-31 20:24:43 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,850,601 · 23 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
1w02w16w27w29w310w311w112w214w419w020w021w122w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab60dc09…85e4
0x34b655…2a6f
8 touches
6 conflicts
0xbfd63419…10ed
0xd32edf…ff58
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x2bbc0cfb…c2be
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
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 0xab60dc0972…4c85e4
Audit this contract →
← previous block·next block →recent activity