← previous blocknext block →recent activity
Analyzing
Block #84,514,790
6 transactions · 5 stateful · 2026-06-29 18:04:24 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,514,790 · 6 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
1w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8279ae9…f9f9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2cb1c883…64c9
0x34b655…2a6f
2 touches
0 conflicts
0x482f3ed7…3307
0x34b655…2a6f
2 touches
0 conflicts
0x482f3ed7…3308
0x34b655…2a6f
2 touches
0 conflicts
0x612d6376…91f4
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 0xa8279ae941…15f9f9
Audit this contract →
← previous block·next block →recent activity