← previous blocknext block →recent activity
Analyzing
Block #106,193,434
26 transactions · 25 stateful · 2026-09-19 13:50:32 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,193,434 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w17w110w211w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd41f5136…97c6
0x34b655…2a6f
14 touches
21 conflicts
0x3b294b21…8cf8
0x34b655…2a6f
10 touches
10 conflicts
0x8d175439…fb79
0x34b655…2a6f
8 touches
6 conflicts
0x74c5eacc…8c94
0x34b655…2a6f
8 touches
6 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity