← previous blocknext block →recent activity
Analyzing
Block #100,701,026
12 transactions · 10 stateful · 2026-08-31 07:51:52 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,701,026 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3c7c65d0…0b52
0x34b655…2a6f
2 touches
0 conflicts
0x62f4ff1a…dc60
0x34b655…2a6f
2 touches
0 conflicts
0x69ce91f4…4602
0x34b655…2a6f
2 touches
0 conflicts
0x6fb5defd…bf67
0x34b655…2a6f
2 touches
0 conflicts
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 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity