← previous blocknext block →recent activity
Analyzing
Block #106,184,791
59 transactions · 46 stateful · 2026-09-19 13:07:03 UTC
Parallelism
75/100
Blocked
72%
Avg conflicts / tx
1.58
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,184,791 · 59 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w29w010w111w012w113w220w321w423w124w125w226w327w437w340w443w349w950w1054w1455w257w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27f401e8…a4fe
0x34b655…2a6f
12 touches
15 conflicts
0x8dd36ab5…9da1
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
10 touches
10 conflicts
0x1a29c64d…e772
0x34b655…2a6f
8 touches
6 conflicts
0x2631b5d1…886b
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
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
15 conflicts on slot 0x27f401e818…6aa4fe
Audit this contract →
← previous block·next block →recent activity