← previous blocknext block →recent activity
Analyzing
Block #105,432,921
11 transactions · 10 stateful · 2026-09-16 22:00:28 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,432,921 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xee8237bd…46ad
0x34b655…2a6f
4 touches
1 conflict
0x9669f551…0690
0x34b655…2a6f
4 touches
1 conflict
0x17091c69…e7f3
0x34b655…2a6f
2 touches
0 conflicts
0x22add0de…0464
0x34b655…2a6f
2 touches
0 conflicts
0x3caf543d…570c
0x34b655…2a6f
2 touches
0 conflicts
0x62ab5018…bc33
0x34b655…2a6f
2 touches
0 conflicts
0x89bc46ca…94c4
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity