← previous blocknext block →recent activity
Analyzing
Block #106,585,345
32 transactions · 29 stateful · 2026-09-20 22:43:02 UTC
Parallelism
94/100
Blocked
14%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,585,345 · 32 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
1w02w13w04w014w015w119w128w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb654bd89…a83b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdf717eac…a7e8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1a79e9de…99e6
0x851145…3f07
4 touches
1 conflict
0xc73fd549…2e28
0x851145…3f07
4 touches
1 conflict
0xd840c9df…2d85
0x851145…3f07
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 0xb654bd89ad…dba83b
Audit this contract →
← previous block·next block →recent activity