← previous blocknext block →recent activity
Analyzing
Block #105,849,169
60 transactions · 48 stateful · 2026-09-18 08:56:53 UTC
Parallelism
78/100
Blocked
73%
Avg conflicts / tx
2.12
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,849,169 · 60 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w07w18w010w213w014w015w116w017w118w219w331w132w336w137w238w340w446w247w548w449w656w458w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
26 touches
78 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x97e4c862…4419
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x896164ea…aa04
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 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: 0xf5b5f7f8…a36d70
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity