← previous blocknext block →recent activity
Analyzing
Block #100,630,049
27 transactions · 25 stateful · 2026-08-31 01:54:51 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,630,049 · 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
1w03w04w05w16w07w08w112w114w216w117w118w223w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x779d5442…54c7
0x34b655…2a6f
6 touches
3 conflicts
0xb5924647…4cf1
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x59cc8c76…75a1
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 0x779d544208…0654c7
Audit this contract →
← previous block·next block →recent activity