← previous blocknext block →recent activity
Analyzing
Block #102,251,191
51 transactions · 27 stateful · 2026-09-05 18:05:02 UTC
Parallelism
88/100
Blocked
52%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,251,191 · 51 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w010w111w212w313w426w530w143w244w446w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x77ed432f…fa04
0x065c9d…c394
8 touches
6 conflicts
0x95523e2a…4c01
0x065c9d…c394
8 touches
6 conflicts
0x26048c96…31fd
0xd32edf…ff58
7 touches
6 conflicts
0x06e40499…165e
0x34ae4d…3fc5
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
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: Kuru Exchange: MarginAccount
15 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity