← previous blocknext block →recent activity
Analyzing
Block #105,576,878
24 transactions · 21 stateful · 2026-09-17 10:04:56 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,576,878 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w111w213w314w215w316w417w518w419w522w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xd1448207…452d
0x34b655…2a6f
8 touches
6 conflicts
0xab41643c…f9bf
0x34b655…2a6f
8 touches
6 conflicts
0x5be35857…0033
0x34b655…2a6f
8 touches
6 conflicts
0x213b816c…a5e0
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x84315ab4…9def
0x34b655…2a6f
6 touches
3 conflicts
0x89999c15…fdac
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 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity