← previous blocknext block →recent activity
Analyzing
Block #105,581,274
22 transactions · 14 stateful · 2026-09-17 10:27:03 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,581,274 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
14w015w116w217w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213b816c…a5e0
0x34b655…2a6f
8 touches
6 conflicts
0x6a2154b8…48e5
0x34b655…2a6f
8 touches
6 conflicts
0x70f537e8…399b
0x34b655…2a6f
8 touches
6 conflicts
0x9c9e7af8…4b29
0x34b655…2a6f
8 touches
6 conflicts
0xca608d0c…f23b
0x34b655…2a6f
8 touches
6 conflicts
0x0eac7709…66c3
0x34b655…2a6f
8 touches
6 conflicts
0x5c9846b4…8bdd
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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: Perpl
6 conflicts on slot 0x213b816cc7…d4a5e0
Audit this contract →
← previous block·next block →recent activity