← previous blocknext block →recent activity
Analyzing
Block #103,210,696
23 transactions · 21 stateful · 2026-09-09 02:52:01 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,210,696 · 23 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
4w05w16w27w38w09w110w011w112w019w221w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdecb9ef3…51c5
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
6 touches
3 conflicts
0x5f40adf2…e754
0x34b655…2a6f
6 touches
3 conflicts
0x668f8210…b140
0x34b655…2a6f
6 touches
3 conflicts
0x676707df…0e0a
0x34b655…2a6f
6 touches
3 conflicts
0x6cfcfad5…7f1b
0x34b655…2a6f
6 touches
3 conflicts
0x76a639da…08f7
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xdecb9ef317…6151c5
Audit this contract →
← previous block·next block →recent activity