← previous blocknext block →recent activity
Analyzing
Block #84,454,211
20 transactions · 14 stateful · 2026-06-29 11:20:10 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,454,211 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w311w413w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x86dbf0…eb2d
10 touches
10 conflicts
0x61d65579…ee3c
0xad96c3…8d7c
10 touches
10 conflicts
0xd821cffd…3ff0
0x754704…b603
10 touches
10 conflicts
0x56a919c4…ab49
0xad96c3…8d7c
8 touches
6 conflicts
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…001b
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: 0x86dbf004…c2eb2d
10 conflicts on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity