← previous blocknext block →recent activity
Analyzing
Block #102,291,513
15 transactions · 15 stateful · 2026-09-05 21:29:24 UTC
Parallelism
47/100
Blocked
47%
Avg conflicts / tx
1.87
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,291,513 · 15 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
1w02w15w26w38w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x5779dbb8…72a4
0x34b655…2a6f
10 touches
10 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x0d2d23d3…8a3a
0x34b655…2a6f
6 touches
3 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x85b3fb19…d4f9
0x34b655…2a6f
4 touches
1 conflict
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity