← previous blocknext block →recent activity
Analyzing
Block #83,655,083
11 transactions · 11 stateful · 2026-06-25 18:33:49 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,655,083 · 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
2w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b671f01…b68f
0x34b655…2a6f
4 touches
1 conflict
0x1c48b3ac…a03c
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd064a456…b881
0x34b655…2a6f
4 touches
1 conflict
0x46d5a052…ff2e
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0x5b671f01c0…00b68f
Audit this contract →
← previous block·next block →recent activity