← previous blocknext block →recent activity
Analyzing
Block #106,934,786
20 transactions · 19 stateful · 2026-09-22 04:02:49 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,786 · 20 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
2w03w14w06w18w09w110w211w312w413w515w618w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x232b0b19…d946
0x34b655…2a6f
14 touches
21 conflicts
0x38f35688…f1af
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0x23c8c8dd…7a42
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x76832384…dc5b
0x34b655…2a6f
4 touches
1 conflict
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 0x232b0b19e0…d1d946
Audit this contract →
← previous block·next block →recent activity