← previous blocknext block →recent activity
Analyzing
Block #84,317,746
19 transactions · 14 stateful · 2026-06-28 20:10:36 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,317,746 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w19w015w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x610aa855…5ecd
0x34b655…2a6f
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
6 touches
3 conflicts
0x5c2680c4…1265
0x34b655…2a6f
4 touches
1 conflict
0x369a11e2…566f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0a82ef74…6501
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xe2263bea…6aa0
0x69df8a…6292
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
3 conflicts on slot 0x610aa855f6…ba5ecd
Audit this contract →
← previous block·next block →recent activity