← previous blocknext block →recent activity
Analyzing
Block #106,539,576
24 transactions · 21 stateful · 2026-09-20 18:52:41 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,539,576 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w112w013w014w117w218w019w320w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45f540f1…05fb
0x34b655…2a6f
8 touches
6 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
8 touches
6 conflicts
0x0c0ca07f…b78d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfac38cc8…fb9d
0x34b655…2a6f
4 touches
1 conflict
0x2ac7f66e…e903
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
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 0x45f540f13a…e905fb
Audit this contract →
← previous block·next block →recent activity