← previous blocknext block →recent activity
Analyzing
Block #106,027,396
23 transactions · 17 stateful · 2026-09-18 23:54:56 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,027,396 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w19w213w217w220w021w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x197c6711…a146
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0x304ce1c3…a4db
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity