← previous blocknext block →recent activity
Analyzing
Block #100,732,536
17 transactions · 15 stateful · 2026-08-31 10:30:23 UTC
Parallelism
65/100
Blocked
33%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,732,536 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w110w011w212w313w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce41e1e6…159f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x68531239…e9a3
0x34b655…2a6f
6 touches
3 conflicts
0xac389ba9…8b45
0x34b655…2a6f
6 touches
3 conflicts
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x3ff1d113…b6d4
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
6 conflicts on slot 0xce41e1e65b…06159f
Audit this contract →
← previous block·next block →recent activity