← previous blocknext block →recent activity
Analyzing
Block #83,624,268
19 transactions · 18 stateful · 2026-06-25 15:08:04 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,624,268 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w213w314w415w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e4fdba3…18f1
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x1e9a1f5b…7da2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4efb974a…6126
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
3 conflicts on slot 0x8e4fdba382…b918f1
Audit this contract →
← previous block·next block →recent activity