← previous blocknext block →recent activity
Analyzing
Block #100,588,660
25 transactions · 20 stateful · 2026-08-30 22:26:38 UTC
Parallelism
84/100
Blocked
45%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,588,660 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w111w218w019w120w321w122w324w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76622fb2…4f08
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x08d53462…97ef
0x2b46c0…1669
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
4 touches
1 conflict
0x62811193…1867
0x2b46c0…1669
4 touches
1 conflict
0x62811193…1869
0x2b46c0…1669
4 touches
1 conflict
0x62811193…186a
0x2b46c0…1669
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
4 touches
1 conflict
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
6 conflicts on slot 0x76622fb2e3…024f08
Audit this contract →
← previous block·next block →recent activity