← previous blocknext block →recent activity
Analyzing
Block #84,616,269
18 transactions · 17 stateful · 2026-06-30 05:21:18 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,616,269 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w110w011w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x159b8597…48a4
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x40b5f387…a164
0x34b655…2a6f
6 touches
3 conflicts
0x3149127f…19a9
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0xca3931f0…0855
0x34b655…2a6f
4 touches
1 conflict
0xcbc53a25…3fa3
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 0x159b8597f3…8f48a4
Audit this contract →
← previous block·next block →recent activity