← previous blocknext block →recent activity
Analyzing
Block #102,211,117
30 transactions · 28 stateful · 2026-09-05 14:42:02 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,211,117 · 30 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
2w03w14w25w36w47w59w010w111w212w316w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa605468c…1bfc
0x34ae4d…3fc5
12 touches
15 conflicts
0x06e40499…165e
0x34ae4d…3fc5
12 touches
15 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
12 touches
15 conflicts
0x77ed432f…fa04
0x065c9d…c394
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 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: 0x34ae4d08…a73fc5
15 conflicts on slot 0xa605468c6d…6d1bfc
Audit this contract →
← previous block·next block →recent activity