← previous blocknext block →recent activity
Analyzing
Block #106,215,759
23 transactions · 19 stateful · 2026-09-19 15:42:57 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,215,759 · 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
1w02w03w14w214w016w317w018w121w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3439deb5…2fa4
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
4 touches
1 conflict
0x7f4a8466…f2cc
0x34ae4d…3fc5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x73b87bc2…457a
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: 0x40c49f17…d22af0
3 conflicts on slot 0x3439deb509…3d2fa4
Audit this contract →
← previous block·next block →recent activity