← previous blocknext block →recent activity
Analyzing
Block #100,584,284
20 transactions · 19 stateful · 2026-08-30 22:04:37 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,584,284 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w49w110w011w112w513w114w615w218w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b7fe709…9d99
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
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
6 conflicts on slot 0x8b7fe70996…af9d99
Audit this contract →
← previous block·next block →recent activity