← previous blocknext block →recent activity
Analyzing
Block #81,458,352
13 transactions · 13 stateful · 2026-06-15 14:09:01 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,458,352 · 13 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
1w02w13w24w25w09w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd0ba6b93…bb4d
0x34b655…2a6f
4 touches
1 conflict
0x006ee1d9…5485
0xa6afd3…d132
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xbcdee322…f454
0xa6afd3…d132
4 touches
1 conflict
0xa318f732…8ae0
0xa6afd3…d132
3 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 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: 0xa6afd386…b0d132
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity