← previous blocknext block →recent activity
Analyzing
Block #106,934,766
16 transactions · 16 stateful · 2026-09-22 04:02:43 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,766 · 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
1w02w13w25w06w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x232b0b19…d946
0x34b655…2a6f
14 touches
21 conflicts
0x38f35688…f1af
0x34b655…2a6f
14 touches
21 conflicts
0x7b242eb5…e60b
0xd32edf…ff58
5 touches
3 conflicts
0x6c6f37ba…c20a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity