← previous blocknext block →recent activity
Analyzing
Block #102,095,187
35 transactions · 33 stateful · 2026-09-05 04:54:25 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
1.89
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #102,095,187 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w16w27w38w49w514w215w318w219w324w426w527w628w734w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x62bb20db…431e
0x34b655…2a6f
14 touches
21 conflicts
0xd162e99a…58de
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c3
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity