← previous blocknext block →recent activity
Analyzing
Block #105,608,224
38 transactions · 22 stateful · 2026-09-17 12:42:43 UTC
Parallelism
87/100
Blocked
50%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,608,224 · 38 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w09w110w211w112w023w024w225w326w027w128w229w330w331w437w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63604530…8ed5
0x34b655…2a6f
8 touches
6 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
8 touches
6 conflicts
0x48132b64…8e95
0x34b655…2a6f
8 touches
6 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x63604530b0…328ed5
Audit this contract →
← previous block·next block →recent activity