← previous blocknext block →recent activity
Analyzing
Block #83,666,761
11 transactions · 10 stateful · 2026-06-25 19:51:39 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,666,761 · 11 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
1w03w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c53a187…3646
0x34b655…2a6f
4 touches
1 conflict
0x7f85816c…3f08
0x34b655…2a6f
4 touches
1 conflict
0xe6fd65c0…3a8a
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x1f50fd2c…91dd
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x374fc18a…6998
0x34b655…2a6f
2 touches
0 conflicts
0x4b2e934b…b94f
0x34b655…2a6f
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 0x2c53a187ea…bc3646
Audit this contract →
← previous block·next block →recent activity