← previous blocknext block →recent activity
Analyzing
Block #105,445,305
16 transactions · 16 stateful · 2026-09-16 23:02:47 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,445,305 · 16 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
2w03w07w18w210w112w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c3d08c7…037d
0x34b655…2a6f
8 touches
6 conflicts
0x93f55e4e…62a3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0x835f7036…38b0
0x34b655…2a6f
4 touches
1 conflict
0xaa7a9163…f79b
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x5c3d08c769…20037d
Audit this contract →
← previous block·next block →recent activity