← previous blocknext block →recent activity
Analyzing
Block #106,367,195
17 transactions · 16 stateful · 2026-09-20 04:25:05 UTC
Parallelism
53/100
Blocked
56%
Avg conflicts / tx
1.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,367,195 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w29w410w512w314w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b590367…87b7
0x34b655…2a6f
14 touches
21 conflicts
0xde00fca6…3969
0x34b655…2a6f
14 touches
21 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
12 touches
15 conflicts
0x3ca268be…8865
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x74e46435…fdcd
0x34b655…2a6f
6 touches
3 conflicts
0x0262e1c6…52e1
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
21 conflicts on slot 0x9b59036767…8b87b7
Audit this contract →
← previous block·next block →recent activity