← previous blocknext block →recent activity
Analyzing
Block #106,539,543
25 transactions · 24 stateful · 2026-09-20 18:52:31 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,539,543 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a2896a0…2a0a
0x34b655…2a6f
16 touches
28 conflicts
0x963a91cf…b871
0x34b655…2a6f
12 touches
15 conflicts
0x3b6e959d…158f
0x34b655…2a6f
10 touches
10 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x0df90aad…3d18
0x34b655…2a6f
8 touches
6 conflicts
0xaa212c38…e996
0x34b655…2a6f
8 touches
6 conflicts
0x93f709d7…11e6
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x2a2896a01b…cc2a0a
Audit this contract →
← previous block·next block →recent activity