← previous blocknext block →recent activity
Analyzing
Block #84,362,972
10 transactions · 10 stateful · 2026-06-29 01:12:09 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,362,972 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w07w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b2dce58…2f1d
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xf112f590…680b
0x34b655…2a6f
4 touches
1 conflict
0xf997c4c7…617d
0x34b655…2a6f
4 touches
1 conflict
0xfe159866…af27
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x1f4c0bac…2da8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
3 conflicts on slot 0x2b2dce5827…4f2f1d
Audit this contract →
← previous block·next block →recent activity