← previous blocknext block →recent activity
Analyzing
Block #106,252,402
17 transactions · 16 stateful · 2026-09-19 18:47:25 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,252,402 · 17 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
1w02w15w26w27w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0547a894…b48b
0x34b655…2a6f
16 touches
28 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
10 touches
10 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x8717d92b…a053
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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
28 conflicts on slot 0x0547a8949d…19b48b
Audit this contract →
← previous block·next block →recent activity