← previous blocknext block →recent activity
Analyzing
Block #106,950,728
23 transactions · 23 stateful · 2026-09-22 05:23:04 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,950,728 · 23 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
2w03w04w05w16w210w111w212w113w314w415w217w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e0846cb…3067
0x34b655…2a6f
8 touches
6 conflicts
0x941bd594…21fd
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xf30b9357…2e1e
0x34b655…2a6f
6 touches
3 conflicts
0x2f9a670b…86d8
0x34b655…2a6f
6 touches
3 conflicts
0x86566137…bad9
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
6 conflicts on slot 0x3e0846cb8f…483067
Audit this contract →
← previous block·next block →recent activity