← previous blocknext block →recent activity
Analyzing
Block #106,224,569
29 transactions · 26 stateful · 2026-09-19 16:27:17 UTC
Parallelism
52/100
Blocked
58%
Avg conflicts / tx
2.14
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,224,569 · 29 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w110w215w317w118w419w520w621w722w823w924w1025w1126w1227w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c6ab626…997f
0x34b655…2a6f
18 touches
36 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x67cb0bae…52c3
0x34b655…2a6f
10 touches
10 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
8 touches
6 conflicts
0x24ed74ea…a3ff
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
36 conflicts on slot 0x5c6ab6266e…9a997f
Audit this contract →
← previous block·next block →recent activity