← previous blocknext block →recent activity
Analyzing
Block #84,047,864
21 transactions · 20 stateful · 2026-06-27 14:12:58 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,047,864 · 21 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
1w04w05w16w07w19w010w111w212w314w118w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0x3de5fb8b…400a
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x9c8d6dd6…d61a
0xea1b8e…c5ec
4 touches
1 conflict
0x9c8d6dd6…d61d
0xea1b8e…c5ec
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity