← previous blocknext block →recent activity
Analyzing
Block #106,224,305
27 transactions · 25 stateful · 2026-09-19 16:25:57 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.15
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,224,305 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w28w310w411w512w213w514w615w716w817w926w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc737ce4f…a8d8
0x34b655…2a6f
14 touches
21 conflicts
0xd939cd66…d68f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x690cb4c2…2ba3
0x34b655…2a6f
10 touches
10 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
8 touches
6 conflicts
0xa6464996…3af9
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
21 conflicts on slot 0xc737ce4f46…1fa8d8
Audit this contract →
← previous block·next block →recent activity