← previous blocknext block →recent activity
Analyzing
Block #100,751,001
16 transactions · 16 stateful · 2026-08-31 12:03:16 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,751,001 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w18w210w311w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8311570f…5321
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x94af8c30…94fb
0x34b655…2a6f
4 touches
1 conflict
0x382434ca…96b5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe15aaadf…bcb7
0x34b655…2a6f
4 touches
1 conflict
0x329f9fde…fe9c
0x34b655…2a6f
2 touches
0 conflicts
0x37c28c7e…e8dd
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
10 conflicts on slot 0x8311570feb…ae5321
Audit this contract →
← previous block·next block →recent activity