← previous blocknext block →recent activity
Analyzing
Block #100,583,389
38 transactions · 28 stateful · 2026-08-30 22:00:07 UTC
Parallelism
82/100
Blocked
54%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,583,389 · 38 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w08w19w213w115w218w319w020w021w122w023w125w127w231w132w233w334w436w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7c68d10b…8386
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x08d53462…97ef
0x2b46c0…1669
6 touches
3 conflicts
0x4e804b48…ef71
0x2b46c0…1669
6 touches
3 conflicts
0x61218f00…5108
0x2b46c0…1669
6 touches
3 conflicts
0x66d63204…51a0
0x2b46c0…1669
6 touches
3 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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity