← previous blocknext block →recent activity
Analyzing
Block #84,730,923
12 transactions · 11 stateful · 2026-06-30 18:05:12 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,730,923 · 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
2w03w16w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x060e767d…0ebb
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x15e3c46c…e3fb
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x4a452241…c216
0x34b655…2a6f
4 touches
1 conflict
0x58650df2…36b1
0x34b655…2a6f
4 touches
1 conflict
0x6ddc5a74…5ec2
0x34b655…2a6f
4 touches
1 conflict
0x71adb892…2a39
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 0x060e767df5…dc0ebb
Audit this contract →
← previous block·next block →recent activity