← previous blocknext block →recent activity
Analyzing
Block #105,843,851
36 transactions · 32 stateful · 2026-09-18 08:30:06 UTC
Parallelism
89/100
Blocked
44%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,843,851 · 36 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w09w010w011w113w116w017w120w021w122w223w224w125w226w227w330w133w034w135w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ba80824…4a64
0x34b655…2a6f
6 touches
3 conflicts
0xeebacabb…a34c
0x34b655…2a6f
6 touches
3 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xec7d120d…7084
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
3 conflicts on slot 0x3ba80824be…c94a64
Audit this contract →
← previous block·next block →recent activity