← previous blocknext block →recent activity
Analyzing
Block #105,540,161
26 transactions · 25 stateful · 2026-09-17 07:00:08 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,540,161 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w18w29w010w111w012w113w014w115w218w119w224w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67c1f465…38b3
0x34b655…2a6f
6 touches
3 conflicts
0xf36124ad…c08f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0xc853be2d…b18f
0x34b655…2a6f
6 touches
3 conflicts
0x897879a1…9c78
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
3 conflicts on slot 0x67c1f46537…4d38b3
Audit this contract →
← previous block·next block →recent activity