← previous blocknext block →recent activity
Analyzing
Block #84,570,435
14 transactions · 12 stateful · 2026-06-30 00:15:53 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,570,435 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebd8c9b0…2ba6
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xb251976b…4938
0x34b655…2a6f
6 touches
3 conflicts
0x52163873…f09f
0x34b655…2a6f
5 touches
3 conflicts
0x5a345314…39fe
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x7bc74ef3…0fee
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
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
6 conflicts on slot 0xebd8c9b046…352ba6
Audit this contract →
← previous block·next block →recent activity