← previous blocknext block →recent activity
Analyzing
Block #84,359,992
23 transactions · 18 stateful · 2026-06-29 00:52:18 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,359,992 · 23 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
7w08w09w110w111w212w213w314w115w016w117w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6fd7409…16b7
0x8fbe07…71b6
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0494780e…2900
0x8fbe07…71b6
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd7add284…8d28
0x34b655…2a6f
4 touches
1 conflict
0x5ebb19ec…ce9a
0xdde003…c9a4
4 touches
1 conflict
0xb983f9fc…9b91
0xdde003…c9a4
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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: 0x8fbe0741…fa71b6
3 conflicts on slot 0xa6fd7409b3…2516b7
Audit this contract →
← previous block·next block →recent activity