← previous blocknext block →recent activity
Analyzing
Block #84,360,436
34 transactions · 23 stateful · 2026-06-29 00:55:15 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,360,436 · 34 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
1w03w04w15w26w18w010w116w120w222w024w128w029w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2f4d415d…5f95
0x34b655…2a6f
6 touches
3 conflicts
0x69941f7e…3b1d
0x34b655…2a6f
6 touches
3 conflicts
0xcde75077…ccee
0x34b655…2a6f
6 touches
3 conflicts
0x265a8eb1…8b43
0xd32edf…ff58
5 touches
3 conflicts
0x7500c6c7…6b90
0x34b655…2a6f
4 touches
1 conflict
0x7c6984da…21e5
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity