← previous blocknext block →recent activity
Analyzing
Block #106,934,579
15 transactions · 15 stateful · 2026-09-22 04:01:46 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,579 · 15 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
3w04w15w06w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e58deff…c5d0
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xdfac0724…d23e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x062c7158…7feb
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
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 0x4e58deff76…56c5d0
Audit this contract →
← previous block·next block →recent activity