← previous blocknext block →recent activity
Analyzing
Block #84,249,779
13 transactions · 13 stateful · 2026-06-28 12:37:52 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,249,779 · 13 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
7w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06a6e99…1623
0x34b655…2a6f
4 touches
1 conflict
0xb6bc6efb…ad9b
0x34b655…2a6f
4 touches
1 conflict
0xd1a241cf…dae4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdf8fc0a1…2dc0
0x34b655…2a6f
4 touches
1 conflict
0xe07a452c…dd18
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x1bdda86b…490d
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
1 conflict on slot 0xf06a6e99f9…1c1623
Audit this contract →
← previous block·next block →recent activity