← previous blocknext block →recent activity
Analyzing
Block #84,460,937
30 transactions · 24 stateful · 2026-06-29 12:05:02 UTC
Parallelism
90/100
Blocked
46%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,460,937 · 30 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
1w02w13w24w15w28w09w110w214w015w117w118w020w226w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x9c4d06ad…be6e
0xd32edf…ff58
5 touches
3 conflicts
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0x729c91b8…9538
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
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: 0xd637b38f…c64160
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity