← previous blocknext block →recent activity
Analyzing
Block #105,608,664
20 transactions · 19 stateful · 2026-09-17 12:44:56 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,608,664 · 20 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
1w02w13w06w27w08w111w113w314w415w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54246aca…5723
0x34b655…2a6f
8 touches
6 conflicts
0x91cdfdeb…7feb
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
6 touches
3 conflicts
0x0a2131b3…455e
0x34b655…2a6f
6 touches
3 conflicts
0x8f84702c…c5f9
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
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
6 conflicts on slot 0x54246acaaf…e55723
Audit this contract →
← previous block·next block →recent activity