← previous blocknext block →recent activity
Analyzing
Block #100,248,316
12 transactions · 11 stateful · 2026-08-29 17:51:15 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,248,316 · 12 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
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5107de9…502c
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0xcc282b3d…e139
0x34b655…2a6f
4 touches
1 conflict
0x3a916aa2…01f0
0x34b655…2a6f
4 touches
1 conflict
0xc2beb645…949d
0x34b655…2a6f
3 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
2 touches
0 conflicts
0x9ca6fa7b…aeb3
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 0xf5107de9a6…e5502c
Audit this contract →
← previous block·next block →recent activity