← previous blocknext block →recent activity
Analyzing
Block #84,181,657
12 transactions · 12 stateful · 2026-06-28 05:03:55 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,181,657 · 12 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x003e3399…a0a5
0x34b655…2a6f
2 touches
0 conflicts
0x19bfb0e5…73b4
0x34b655…2a6f
2 touches
0 conflicts
0x2a6f44f7…86c4
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x508005f9…440e
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x085df2c147…d2305a
Audit this contract →
← previous block·next block →recent activity