← previous blocknext block →recent activity
Analyzing
Block #84,130,052
18 transactions · 17 stateful · 2026-06-27 23:20:38 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,130,052 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w17w08w09w110w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0c2e8d…c1b8
0xe52b14…7230
6 touches
3 conflicts
0x5149ba0e…d954
0x754704…b603
6 touches
3 conflicts
0x09a15b10…2639
0x754704…b603
6 touches
3 conflicts
0x532023a5…d800
0xe52b14…7230
6 touches
3 conflicts
0x8ffa3328…ce11
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0xf2e7bb96…1a58
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: 0xe52b1424…bb7230
3 conflicts on slot 0x0b0c2e8d5e…dbc1b8
Audit this contract →
← previous block·next block →recent activity