← previous blocknext block →recent activity
Analyzing
Block #106,452,940
18 transactions · 18 stateful · 2026-09-20 11:36:40 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,452,940 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w18w29w310w411w012w413w114w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb46c7ade…d4b0
0x34b655…2a6f
14 touches
21 conflicts
0x8d664414…3344
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
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
21 conflicts on slot 0xb46c7ade7f…44d4b0
Audit this contract →
← previous block·next block →recent activity