← previous blocknext block →recent activity
Analyzing
Block #83,452,542
31 transactions · 25 stateful · 2026-06-24 20:02:16 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,452,542 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w19w113w114w015w017w018w126w127w228w329w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x829970ec…4748
0xd32edf…ff58
5 touches
3 conflicts
0x049cca71…b102
0x34b655…2a6f
4 touches
1 conflict
0xa02e5cdd…76b8
0x34b655…2a6f
4 touches
1 conflict
0xbb3504d4…b05f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity