← previous blocknext block →recent activity
Analyzing
Block #107,794,789
21 transactions · 17 stateful · 2026-09-25 04:14:01 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,794,789 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w28w09w110w311w114w015w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ff9db2e…22f6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
6 touches
3 conflicts
0x8d919576…ff85
0xd32edf…ff58
5 touches
3 conflicts
0x0311862a…7c5c
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
6 conflicts on slot 0x3ff9db2e2d…9122f6
Audit this contract →
← previous block·next block →recent activity