← previous blocknext block →recent activity
Analyzing
Block #100,700,043
21 transactions · 21 stateful · 2026-08-31 07:46:55 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,700,043 · 21 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
2w03w15w07w18w210w012w113w014w115w218w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x7150753f…7e32
0x34b655…2a6f
4 touches
1 conflict
0x7b0297c7…8f17
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity