← previous blocknext block →recent activity
Analyzing
Block #105,921,130
33 transactions · 30 stateful · 2026-09-18 14:59:56 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.79
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,921,130 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w49w510w611w712w831w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x12e605da…9ca3
0x34b655…2a6f
16 touches
28 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
16 touches
28 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
16 touches
28 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
16 touches
28 conflicts
0x739123da…57f3
0x34b655…2a6f
16 touches
28 conflicts
0x821e96f4…6d12
0x34b655…2a6f
16 touches
28 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
36 conflicts on slot 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity