← previous blocknext block →recent activity
Analyzing
Block #105,410,276
31 transactions · 31 stateful · 2026-09-16 20:06:30 UTC
Parallelism
52/100
Blocked
68%
Avg conflicts / tx
2.97
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,410,276 · 31 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w39w110w211w312w413w514w615w716w817w918w1019w1121w423w126w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0x100812e9…12b7
0x34b655…2a6f
12 touches
15 conflicts
0x672d5d58…1af8
0x34b655…2a6f
10 touches
10 conflicts
0x74cdc294…26a8
0x34b655…2a6f
10 touches
10 conflicts
0x75f36d60…8556
0x34b655…2a6f
10 touches
10 conflicts
0x86ecf291…f692
0x34b655…2a6f
10 touches
10 conflicts
0x8b7e5c4e…5fae
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity