← previous blocknext block →recent activity
Analyzing
Block #105,930,639
26 transactions · 23 stateful · 2026-09-18 15:47:48 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,930,639 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w210w011w115w116w317w419w520w621w022w125w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60b7b268…2074
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x17d87f0d…bfc5
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x0e4fa697…08ca
0x34b655…2a6f
4 touches
1 conflict
0x2fba77e7…bea1
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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
21 conflicts on slot 0x60b7b268bd…fe2074
Audit this contract →
← previous block·next block →recent activity