← previous blocknext block →recent activity
Analyzing
Block #106,428,537
21 transactions · 20 stateful · 2026-09-20 09:33:47 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,428,537 · 21 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
2w03w16w013w014w115w216w317w418w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x282d0473…a801
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x4984f7be…d515
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xa45fa28d…9ded
0x34b655…2a6f
4 touches
1 conflict
0xa7b29d23…096f
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
6 conflicts on slot 0x109d8a5293…02a7b7
Audit this contract →
← previous block·next block →recent activity