← previous blocknext block →recent activity
Analyzing
Block #108,494,344
23 transactions · 22 stateful · 2026-09-27 14:54:49 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,494,344 · 23 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
1w02w15w08w011w212w313w414w315w516w617w718w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x588380ee…0a5c
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xdd77da90…6df4
0x34b655…2a6f
6 touches
3 conflicts
0xef3805c2…a0c5
0x34b655…2a6f
6 touches
3 conflicts
0x62ce5f33…5ecb
0x34b655…2a6f
6 touches
3 conflicts
0xf7213a75…8d13
0x34b655…2a6f
6 touches
3 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
6 touches
3 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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity