← previous blocknext block →recent activity
Analyzing
Block #100,984,240
20 transactions · 19 stateful · 2026-09-01 07:36:55 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,984,240 · 20 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
1w02w13w05w06w08w19w210w211w012w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf38a3927…ad62
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x50ad95fe…e87c
0x065c9d…c394
4 touches
1 conflict
0xce83db54…df2b
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x36836f22…9649
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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 0xf38a392760…8fad62
Audit this contract →
← previous block·next block →recent activity