← previous blocknext block →recent activity
Analyzing
Block #106,800,947
37 transactions · 34 stateful · 2026-09-21 16:49:10 UTC
Parallelism
65/100
Blocked
71%
Avg conflicts / tx
2.19
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,800,947 · 37 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w110w211w313w314w415w516w217w118w621w122w623w724w825w926w1029w236w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6f5d7ccd…83d4
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x9edb7ad7…8d56
0x34b655…2a6f
10 touches
10 conflicts
0xa0454312…cf89
0xd32edf…ff58
9 touches
10 conflicts
0x52f57971…c16b
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
15 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity