← previous blocknext block →recent activity
Analyzing
Block #106,922,287
26 transactions · 26 stateful · 2026-09-22 02:59:55 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,922,287 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w09w010w111w212w313w416w117w118w021w022w124w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c60fbcf…8744
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xc7ce92b1…25d0
0x34b655…2a6f
10 touches
10 conflicts
0x08801f9a…1449
0x34b655…2a6f
4 touches
1 conflict
0x46cbc06b…eb46
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x4d71729b…b045
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
10 conflicts on slot 0x6c60fbcffc…878744
Audit this contract →
← previous block·next block →recent activity