← previous blocknext block →recent activity
Analyzing
Block #107,812,971
28 transactions · 28 stateful · 2026-09-25 05:45:30 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,812,971 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w09w110w011w113w215w016w217w318w419w520w621w722w223w727w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b76a1fb…fdfc
0x34b655…2a6f
10 touches
10 conflicts
0xa23b9051…392f
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x2ea3a28c…c266
0x34b655…2a6f
8 touches
6 conflicts
0x6c6c0a3d…277a
0xd32edf…ff58
7 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
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
10 conflicts on slot 0x2b76a1fb53…5afdfc
Audit this contract →
← previous block·next block →recent activity