← previous blocknext block →recent activity
Analyzing
Block #108,335,734
26 transactions · 23 stateful · 2026-09-27 01:36:31 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.85
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,335,734 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w312w013w114w215w316w017w118w219w323w024w125w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10193197…5cee
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xe483d4e3…e52c
0x1b6862…e19c
8 touches
6 conflicts
0x6c12827b…b70b
0xd32edf…ff58
7 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
6 conflicts on slot 0x10193197c6…7e5cee
Audit this contract →
← previous block·next block →recent activity