← previous blocknext block →recent activity
Analyzing
Block #105,643,340
28 transactions · 24 stateful · 2026-09-17 15:39:31 UTC
Parallelism
86/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,643,340 · 28 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
1w02w03w14w05w06w17w28w39w113w015w016w120w122w224w326w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a1a51b6…0630
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0xe48402d6…728b
0x34b655…2a6f
8 touches
6 conflicts
0xee8237bd…46ad
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x3a1a51b6e3…560630
Audit this contract →
← previous block·next block →recent activity