← previous blocknext block →recent activity
Analyzing
Block #106,235,145
22 transactions · 21 stateful · 2026-09-19 17:20:34 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,235,145 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w010w111w212w313w414w515w616w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf00e711b…c539
0x34b655…2a6f
14 touches
21 conflicts
0x87b91d84…7cd3
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xe3513f72…fe42
0x34b655…2a6f
6 touches
3 conflicts
0x05e1eba1…6491
0x34b655…2a6f
6 touches
3 conflicts
0x5906754f…b584
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x594c7ced…e1cf
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 0xf00e711b37…00c539
Audit this contract →
← previous block·next block →recent activity