← previous blocknext block →recent activity
Analyzing
Block #83,664,899
19 transactions · 18 stateful · 2026-06-25 19:39:13 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,664,899 · 19 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
1w02w13w05w111w012w113w216w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81c5483a…59e8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92a584bc…21e9
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd7513857…4c08
0x34b655…2a6f
6 touches
3 conflicts
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0xa50fcb98…2b01
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
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 0x81c5483add…3e59e8
Audit this contract →
← previous block·next block →recent activity