← previous blocknext block →recent activity
Analyzing
Block #106,200,304
28 transactions · 26 stateful · 2026-09-19 14:25:07 UTC
Parallelism
61/100
Blocked
58%
Avg conflicts / tx
2.29
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,200,304 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w09w210w311w419w520w621w722w823w924w1025w127w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x253561ba…8c1a
0x34b655…2a6f
22 touches
55 conflicts
0x315e07b8…9823
0x34b655…2a6f
16 touches
28 conflicts
0x5717771c…45ed
0x34b655…2a6f
12 touches
15 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
10 touches
10 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
10 touches
10 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
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
55 conflicts on slot 0x253561bad2…698c1a
Audit this contract →
← previous block·next block →recent activity