← previous blocknext block →recent activity
Analyzing
Block #105,852,272
16 transactions · 16 stateful · 2026-09-18 09:12:30 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,852,272 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w19w010w211w312w413w514w615w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56a78e60…72fb
0x34b655…2a6f
14 touches
21 conflicts
0x1f90c530…dd82
0x34b655…2a6f
10 touches
10 conflicts
0x6caf33e2…c261
0x34b655…2a6f
10 touches
10 conflicts
0x89999c15…fdac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
21 conflicts on slot 0x56a78e60a6…3f72fb
Audit this contract →
← previous block·next block →recent activity