← previous blocknext block →recent activity
Analyzing
Block #84,038,779
9 transactions · 9 stateful · 2026-06-27 13:12:30 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,038,779 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x66e47d07…baa6
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x06e40499…165e
0x69df8a…6292
4 touches
1 conflict
0xa605468c…1bfc
0x69df8a…6292
4 touches
1 conflict
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
3 conflicts on slot 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity