← previous blocknext block →recent activity
Analyzing
Block #84,042,771
23 transactions · 22 stateful · 2026-06-27 13:39:05 UTC
Parallelism
91/100
Blocked
5%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,042,771 · 23 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
20w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4658f5c…b257
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2783b888…3ad2
0x065c9d…c394
2 touches
0 conflicts
0x6da19b1c…8936
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
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 0xa4658f5c4c…e0b257
Audit this contract →
← previous block·next block →recent activity