← previous blocknext block →recent activity
Analyzing
Block #100,237,907
18 transactions · 18 stateful · 2026-08-29 16:58:15 UTC
Parallelism
78/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,237,907 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w313w016w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51dc
0x69a5f9…2fef
8 touches
6 conflicts
0xfda39b6f…d4cc
0x754704…b603
8 touches
6 conflicts
0x2ef1d89b…196d
0x754704…b603
8 touches
6 conflicts
0x00000000…0036
0x35a73b…6042
8 touches
6 conflicts
0xaf831072…51d5
0x69a5f9…2fef
8 touches
6 conflicts
0xaf831072…51d6
0x69a5f9…2fef
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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: 0x69a5f9ad…102fef
6 conflicts on slot 0xaf831072f6…c551dc
Audit this contract →
← previous block·next block →recent activity