← previous blocknext block →recent activity
Analyzing
Block #105,461,545
15 transactions · 13 stateful · 2026-09-17 00:24:31 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,461,545 · 15 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
1w04w15w26w17w29w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c0f4ae9…4da1
0x34b655…2a6f
8 touches
6 conflicts
0xd1448207…452d
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x178a61ad…4958
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
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 0x0c0f4ae99e…f34da1
Audit this contract →
← previous block·next block →recent activity