← previous blocknext block →recent activity
Analyzing
Block #106,042,017
26 transactions · 26 stateful · 2026-09-19 01:08:31 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,042,017 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w09w010w112w118w220w021w122w223w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0xaaebbec3…8eea
0x34b655…2a6f
6 touches
3 conflicts
0x2905340c…dbc6
0x34b655…2a6f
5 touches
3 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity