← previous blocknext block →recent activity
Analyzing
Block #105,461,413
10 transactions · 10 stateful · 2026-09-17 00:23:51 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,461,413 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0da07e4…ccf2
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8d616e7c…a6a1
0x34b655…2a6f
4 touches
1 conflict
0xa90eb29b…2cec
0x34b655…2a6f
4 touches
1 conflict
0xaaf36ccb…f35c
0x34b655…2a6f
4 touches
1 conflict
0xb40e601f…bf98
0x34b655…2a6f
4 touches
1 conflict
0xda50c9d5…674e
0x34b655…2a6f
4 touches
1 conflict
0x0bb33e3f…7072
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
1 conflict on slot 0xe0da07e453…abccf2
Audit this contract →
← previous block·next block →recent activity