← previous blocknext block →recent activity
Analyzing
Block #102,277,583
36 transactions · 33 stateful · 2026-09-05 20:18:49 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,277,583 · 36 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w19w010w119w020w124w025w128w229w230w334w035w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a2055c7…9054
0x34b655…2a6f
8 touches
6 conflicts
0x640c4fb2…044a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
8 touches
6 conflicts
0x16c10572…71dc
0x34b655…2a6f
7 touches
6 conflicts
0x82a21578…a099
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x1a2055c785…e29054
Audit this contract →
← previous block·next block →recent activity