← previous blocknext block →recent activity
Analyzing
Block #106,453,217
36 transactions · 27 stateful · 2026-09-20 11:38:04 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,453,217 · 36 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
1w04w17w08w19w013w014w115w217w319w220w323w225w228w329w430w535w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d091c36…3028
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x8ec20502…290f
0x34b655…2a6f
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x2ecffdb2…0a01
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 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
10 conflicts on slot 0x4d091c36e1…553028
Audit this contract →
← previous block·next block →recent activity