← previous blocknext block →recent activity
Analyzing
Block #106,934,815
20 transactions · 20 stateful · 2026-09-22 04:02:58 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,815 · 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
1w03w04w16w07w18w29w310w411w512w614w017w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38f35688…f1af
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x232b0b19…d946
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0x38f356889a…23f1af
Audit this contract →
← previous block·next block →recent activity