← previous blocknext block →recent activity
Analyzing
Block #100,081,348
22 transactions · 18 stateful · 2026-08-29 03:49:53 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,081,348 · 22 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
5w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x124ad1a4…3f63
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x076b9edf…e35c
0x34b655…2a6f
2 touches
0 conflicts
0x1e168c8b…6945
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 0x50c615063f…63343f
Audit this contract →
← previous block·next block →recent activity