← previous blocknext block →recent activity
Analyzing
Block #105,410,869
14 transactions · 14 stateful · 2026-09-16 20:09:29 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,410,869 · 14 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
1w04w05w17w18w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc9c17729…ac91
0x34b655…2a6f
4 touches
1 conflict
0x2557abf8…2901
0x34b655…2a6f
2 touches
0 conflicts
0x6859b6a7…c5ff
0x34b655…2a6f
2 touches
0 conflicts
0x80d105de…593c
0x34b655…2a6f
2 touches
0 conflicts
0x874efddc…5c72
0x34b655…2a6f
2 touches
0 conflicts
0x9d111397…670d
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity