← previous blocknext block →recent activity
Analyzing
Block #105,618,875
16 transactions · 15 stateful · 2026-09-17 13:36:21 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,618,875 · 16 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
2w03w16w07w18w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a58d502…385c
0x34b655…2a6f
6 touches
3 conflicts
0xd5398303…808b
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0x9c9e50af…a6b9
0x34b655…2a6f
4 touches
1 conflict
0xbcdfbff9…f59d
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 0x2a58d5029f…32385c
Audit this contract →
← previous block·next block →recent activity