← previous blocknext block →recent activity
Analyzing
Block #105,932,933
25 transactions · 23 stateful · 2026-09-18 15:59:21 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,932,933 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w17w29w010w112w213w314w015w416w519w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x33303721…96ed
0x34b655…2a6f
4 touches
1 conflict
0x3d6c26e5…1b45
0x34b655…2a6f
4 touches
1 conflict
0x4361ef1c…23ad
0x34b655…2a6f
4 touches
1 conflict
0x4856b443…1824
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity