← previous blocknext block →recent activity
Analyzing
Block #83,401,670
25 transactions · 17 stateful · 2026-06-24 14:22:25 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,401,670 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w211w312w415w217w018w319w420w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x8b305a3b…1c35
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92f3f897…d0ec
0x34b655…2a6f
4 touches
1 conflict
0x93c5495a…b03b
0x34b655…2a6f
4 touches
1 conflict
0x9603d13f…d632
0x34b655…2a6f
4 touches
1 conflict
0x9bcdd44d…efed
0x34b655…2a6f
4 touches
1 conflict
0x9c57dcbc…cc97
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity