← previous blocknext block →recent activity
Analyzing
Block #101,088,047
26 transactions · 24 stateful · 2026-09-01 16:19:34 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,088,047 · 26 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
1w02w04w06w07w08w110w215w016w017w018w119w120w121w222w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0476d77b…a514
0x34b655…2a6f
4 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity