← previous blocknext block →recent activity
Analyzing
Block #84,549,076
17 transactions · 15 stateful · 2026-06-29 21:53:32 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,549,076 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w18w09w110w211w312w415w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3da49e5d…8067
0x34b655…2a6f
8 touches
6 conflicts
0x1c7763f6…89be
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9a5244ed…fc88
0x34b655…2a6f
4 touches
1 conflict
0xa4a2c7be…f5a3
0x34b655…2a6f
4 touches
1 conflict
0xa51c97e1…6b55
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x3da49e5da7…d48067
Audit this contract →
← previous block·next block →recent activity