← previous blocknext block →recent activity
Analyzing
Block #84,335,395
20 transactions · 17 stateful · 2026-06-28 22:08:14 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,335,395 · 20 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
1w02w03w14w17w08w110w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bdcc5ee…7e90
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x350734a0…4a86
0xd32edf…ff58
3 touches
1 conflict
0x58f2fdac…ae86
0x065c9d…c394
2 touches
0 conflicts
0x7ea43b0d…6f76
0x065c9d…c394
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 0x4bdcc5eebf…627e90
Audit this contract →
← previous block·next block →recent activity