← previous blocknext block →recent activity
Analyzing
Block #105,672,456
14 transactions · 12 stateful · 2026-09-17 18:06:05 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,672,456 · 14 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
1w03w14w26w07w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ac6d2b5…e3f0
0x34b655…2a6f
6 touches
3 conflicts
0xb5f5f775…010b
0x34b655…2a6f
6 touches
3 conflicts
0x451a771d…2a72
0x34b655…2a6f
6 touches
3 conflicts
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd676c677…fba6
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 0x1ac6d2b5e4…b4e3f0
Audit this contract →
← previous block·next block →recent activity