← previous blocknext block →recent activity
Analyzing
Block #101,985,067
20 transactions · 20 stateful · 2026-09-04 19:36:09 UTC
Parallelism
80/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,985,067 · 20 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
4w010w113w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x767c56c7…ec85
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x083f43b4…e55c
0x34b655…2a6f
2 touches
0 conflicts
0x0f1cea4a…6758
0x34b655…2a6f
2 touches
0 conflicts
0x19f8e68c…4f86
0x34b655…2a6f
2 touches
0 conflicts
0x1d821a69…b822
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 0x767c56c7b2…9aec85
Audit this contract →
← previous block·next block →recent activity