← previous blocknext block →recent activity
Analyzing
Block #84,248,488
26 transactions · 22 stateful · 2026-06-28 12:29:15 UTC
Parallelism
92/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,248,488 · 26 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w06w07w114w015w116w118w019w121w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b5b2ce…c5bb
0xfa32f9…f3f0
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x1c09b8a6…d9a9
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
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: 0xfa32f9ec…fef3f0
1 conflict on slot 0x38b5b2ceac…4cc5bb
Audit this contract →
← previous block·next block →recent activity