← previous blocknext block →recent activity
Analyzing
Block #100,266,271
16 transactions · 16 stateful · 2026-08-29 19:22:16 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,266,271 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42e917f7…ed8c
0x34b655…2a6f
4 touches
1 conflict
0x831f75b4…945d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x2ed5ccb6…95d6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x41c56387…a8f6
0x34b655…2a6f
2 touches
0 conflicts
0x8e3aa06a…cab9
0x34b655…2a6f
2 touches
0 conflicts
0x9ad325f5…cc43
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 0x42e917f7fa…e0ed8c
Audit this contract →
← previous block·next block →recent activity