← previous blocknext block →recent activity
Analyzing
Block #100,748,667
27 transactions · 21 stateful · 2026-08-31 11:51:31 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,748,667 · 27 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
1w02w13w29w310w011w112w013w114w116w218w325w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x191e0467…70e5
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7a12283f…b18a
0x34ae4d…3fc5
4 touches
1 conflict
0x80caf0f7…f2de
0x34ae4d…3fc5
4 touches
1 conflict
0x8b2c44b4…7e59
0x34ae4d…3fc5
4 touches
1 conflict
0x915c095e…c1e5
0x34ae4d…3fc5
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
10 conflicts on slot 0x191e0467ba…1470e5
Audit this contract →
← previous block·next block →recent activity