← previous blocknext block →recent activity
Analyzing
Block #83,665,851
15 transactions · 15 stateful · 2026-06-25 19:45:35 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,665,851 · 15 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
4w05w06w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xf86f15cd…38af
0x34b655…2a6f
4 touches
1 conflict
0x61df3de4…0ae7
0x34b655…2a6f
4 touches
1 conflict
0xb6b7c45d…9d5a
0x34b655…2a6f
4 touches
1 conflict
0x16dce2e7…6f05
0x34b655…2a6f
2 touches
0 conflicts
0x292c7ec5…3c58
0x34b655…2a6f
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x27f4e3f7…a81e
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity