← previous blocknext block →recent activity
Analyzing
Block #83,984,015
12 transactions · 9 stateful · 2026-06-27 07:07:40 UTC
Parallelism
75/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,984,015 · 12 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
6w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f8a50d…333b
0x34b655…2a6f
4 touches
1 conflict
0x771d59ec…110f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x17cc5ec3…ae0e
0x34b655…2a6f
3 touches
1 conflict
0x0bcaba7e…0e80
0x3bd359…433a
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
2 touches
0 conflicts
0x5f55f2c8…8f11
0x754704…b603
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 0x63f8a50db5…53333b
Audit this contract →
← previous block·next block →recent activity