← previous blocknext block →recent activity
Analyzing
Block #107,450,320
17 transactions · 17 stateful · 2026-09-23 23:18:07 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,450,320 · 17 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
1w02w15w06w17w28w39w310w413w115w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b2
0x37db7f…ec7b
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x63503840…bc70
0x34b655…2a6f
4 touches
1 conflict
0x6bea8866…7f18
0x34b655…2a6f
4 touches
1 conflict
0x779318f6…391a
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: 0x37db7fbf…3eec7b
10 conflicts on slot 0x8a35acfbc1…6bd1b2
Audit this contract →
← previous block·next block →recent activity