← previous blocknext block →recent activity
Analyzing
Block #108,942,573
24 transactions · 24 stateful · 2026-09-29 04:35:00 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,942,573 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w28w39w410w012w013w114w215w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1289b730…560e
0x34b655…2a6f
10 touches
10 conflicts
0x3d93a189…ab80
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0056
0x1b6862…e19c
8 touches
6 conflicts
0x116fb54f…dd2d
0x1b6862…e19c
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 0x1289b730c4…e3560e
Audit this contract →
← previous block·next block →recent activity