← previous blocknext block →recent activity
Analyzing
Block #106,207,878
22 transactions · 21 stateful · 2026-09-19 15:03:17 UTC
Parallelism
59/100
Blocked
62%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,207,878 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w29w310w411w512w613w714w820w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3801c5e5…82ba
0x34b655…2a6f
14 touches
21 conflicts
0xf9470055…bbf8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1f4b78fe…612e
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x00000000…00c9
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
21 conflicts on slot 0x3801c5e5f9…7682ba
Audit this contract →
← previous block·next block →recent activity