← previous blocknext block →recent activity
Analyzing
Block #106,190,909
14 transactions · 14 stateful · 2026-09-19 13:37:50 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,190,909 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w010w111w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708d7a74…09e3
0x34b655…2a6f
6 touches
3 conflicts
0xfda729a6…3a4e
0x34b655…2a6f
4 touches
1 conflict
0x9167c873…748f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd41f5136…97c6
0x34b655…2a6f
4 touches
1 conflict
0xea009aac…4ebf
0x34b655…2a6f
4 touches
1 conflict
0xfcaee83d…428d
0x34b655…2a6f
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
3 conflicts on slot 0x708d7a74a7…5d09e3
Audit this contract →
← previous block·next block →recent activity