← previous blocknext block →recent activity
Analyzing
Block #107,813,478
21 transactions · 20 stateful · 2026-09-25 05:48:03 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,813,478 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w011w112w213w314w415w016w119w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc64d3656…0c1c
0x34b655…2a6f
10 touches
10 conflicts
0xba522812…1f1f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd59f6ed1…03eb
0x1b6862…e19c
8 touches
6 conflicts
0x961c0cd9…0937
0x34b655…2a6f
8 touches
6 conflicts
0x1ae03ff2…30fd
0x34b655…2a6f
8 touches
6 conflicts
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 0xc64d3656b5…c50c1c
Audit this contract →
← previous block·next block →recent activity