← previous blocknext block →recent activity
Analyzing
Block #84,364,924
27 transactions · 23 stateful · 2026-06-29 01:25:09 UTC
Parallelism
93/100
Blocked
22%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,364,924 · 27 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
1w06w09w110w011w114w015w118w122w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a8f8b9c…3046
0x34b655…2a6f
4 touches
1 conflict
0x1564aef8…90c9
0x34b655…2a6f
4 touches
1 conflict
0x2666137c…e4ea
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x75194ada…a1c5
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
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
1 conflict on slot 0x0a8f8b9c32…e53046
Audit this contract →
← previous block·next block →recent activity