← previous blocknext block →recent activity
Analyzing
Block #100,080,439
12 transactions · 10 stateful · 2026-08-29 03:45:18 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,080,439 · 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
6w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x58658217…80ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
2 touches
0 conflicts
0x1f24937e…aeab
0x34b655…2a6f
2 touches
0 conflicts
0x5791ccc0…9a3d
0x34b655…2a6f
2 touches
0 conflicts
0x5ed1f9d0…fc7f
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 0xfcc8f826d7…5f7c5f
Audit this contract →
← previous block·next block →recent activity