← previous blocknext block →recent activity
Analyzing
Block #106,191,188
18 transactions · 16 stateful · 2026-09-19 13:39:14 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,191,188 · 18 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
2w04w06w07w110w111w113w014w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda729a6…3a4e
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x35fefb39…2533
0x34b655…2a6f
2 touches
0 conflicts
0x708d7a74…09e3
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
3 conflicts on slot 0xfda729a6e6…be3a4e
Audit this contract →
← previous block·next block →recent activity