← previous blocknext block →recent activity
Analyzing
Block #84,116,161
8 transactions · 6 stateful · 2026-06-27 21:47:59 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,116,161 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0xa46c1d9e…ff71
0x34b655…2a6f
4 touches
1 conflict
0xc17e5a7e…b95f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe59df86b…a00c
0x34b655…2a6f
4 touches
1 conflict
0x672fd8ba…9e9e
0x34b655…2a6f
4 touches
1 conflict
0x67fc285e…2584
0x34b655…2a6f
2 touches
0 conflicts
0x723d3210…b4e2
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 0x9966da3102…c80d0f
Audit this contract →
← previous block·next block →recent activity