← previous blocknext block →recent activity
Analyzing
Block #106,028,508
22 transactions · 20 stateful · 2026-09-19 00:00:32 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,028,508 · 22 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
1w02w13w04w25w38w110w112w213w314w415w518w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x5d28983e…5c03
0x34b655…2a6f
6 touches
3 conflicts
0x6435bd34…b160
0x34b655…2a6f
6 touches
3 conflicts
0xb05cd4f5…73d0
0x34ae4d…3fc5
4 touches
1 conflict
0xdb067026…9eb8
0x34ae4d…3fc5
4 touches
1 conflict
0x00af2567…c002
0x34b655…2a6f
4 touches
1 conflict
0x0ad1ace1…ceea
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity