← previous blocknext block →recent activity
Analyzing
Block #105,582,131
16 transactions · 14 stateful · 2026-09-17 10:31:22 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,582,131 · 16 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
1w04w17w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe40a656b…a98c
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x45082691…dff7
0x34b655…2a6f
4 touches
1 conflict
0xb0f5bc30…5d12
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x26c599c1…706c
0x34b655…2a6f
2 touches
0 conflicts
0x2a3f40b6…e39c
0x34b655…2a6f
2 touches
0 conflicts
0x39862cf5…39dd
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xe40a656b3a…98a98c
Audit this contract →
← previous block·next block →recent activity