← previous blocknext block →recent activity
Analyzing
Block #106,026,483
16 transactions · 14 stateful · 2026-09-18 23:50:20 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,026,483 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w110w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5cddf91…0abf
0x34b655…2a6f
12 touches
15 conflicts
0x7aad02c6…b979
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0xc2775c92…702a
0x34b655…2a6f
6 touches
3 conflicts
0xf537d3a9…730b
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x99479bc5…3a88
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
15 conflicts on slot 0xb5cddf91cd…9a0abf
Audit this contract →
← previous block·next block →recent activity