← previous blocknext block →recent activity
Analyzing
Block #105,461,513
9 transactions · 9 stateful · 2026-09-17 00:24:21 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,461,513 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0xddfa8a84…68ee
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c912a68…3b21
0x2a68ba…90c5
2 touches
0 conflicts
0x5b6af007…0f35
0x34b655…2a6f
2 touches
0 conflicts
0x8e5003a2…6362
0x34b655…2a6f
2 touches
0 conflicts
0x9c2fc330…0091
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 0x60a536a6ee…6aef7a
Audit this contract →
← previous block·next block →recent activity