← previous blocknext block →recent activity
Analyzing
Block #106,379,655
23 transactions · 19 stateful · 2026-09-20 05:27:47 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,379,655 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w17w110w215w016w117w218w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8058ec4…ebac
0x34b655…2a6f
8 touches
6 conflicts
0x95063b48…269f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x78cc044a…79de
0x34b655…2a6f
4 touches
1 conflict
0xfdd8bfdb…d96f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xe8058ec456…d4ebac
Audit this contract →
← previous block·next block →recent activity