← previous blocknext block →recent activity
Analyzing
Block #106,242,025
28 transactions · 26 stateful · 2026-09-19 17:55:11 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,242,025 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w27w119w020w121w222w323w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76ed8777…1e5f
0x34b655…2a6f
10 touches
10 conflicts
0x36c61357…767b
0x34b655…2a6f
8 touches
6 conflicts
0x9af34906…40ff
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
8 touches
6 conflicts
0xff2ce193…156b
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
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 0x76ed8777f7…0c1e5f
Audit this contract →
← previous block·next block →recent activity