← previous blocknext block →recent activity
Analyzing
Block #106,470,954
25 transactions · 24 stateful · 2026-09-20 13:07:19 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,470,954 · 25 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
1w02w13w24w36w07w18w09w011w012w115w016w118w121w022w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17bb579f…938c
0x34b655…2a6f
8 touches
6 conflicts
0xb7aecdbc…2b79
0x34b655…2a6f
8 touches
6 conflicts
0x30ae635d…5e67
0x34b655…2a6f
6 touches
3 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0x362ac6f5…7b54
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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
6 conflicts on slot 0x17bb579f2c…21938c
Audit this contract →
← previous block·next block →recent activity