← previous blocknext block →recent activity
Analyzing
Block #83,669,259
16 transactions · 15 stateful · 2026-06-25 20:08:21 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,669,259 · 16 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
11w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0xb42ffae8…7bb9
0x34b655…2a6f
4 touches
1 conflict
0xbf5085eb…1d64
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x39e62286…adf1
0x40c49f…2af0
2 touches
0 conflicts
0x6398e5e9…c387
0x40c49f…2af0
2 touches
0 conflicts
0xad41f4ab…810b
0x40c49f…2af0
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 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity