← previous blocknext block →recent activity
Analyzing
Block #100,750,240
12 transactions · 12 stateful · 2026-08-31 11:59:26 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,750,240 · 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
2w04w05w16w08w110w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eaf7514…282c
0x34b655…2a6f
4 touches
1 conflict
0xf14da19e…b066
0x34b655…2a6f
4 touches
1 conflict
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdc9915b5…542c
0x34b655…2a6f
4 touches
1 conflict
0x3c2db66e…31bc
0x34b655…2a6f
2 touches
0 conflicts
0xc10b903d…2f54
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
1 conflict on slot 0x8eaf751445…15282c
Audit this contract →
← previous block·next block →recent activity