← previous blocknext block →recent activity
Analyzing
Block #83,201,058
34 transactions · 26 stateful · 2026-06-23 16:02:11 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,201,058 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w010w013w116w124w227w328w429w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6bdb9869…7558
0x34b655…2a6f
10 touches
10 conflicts
0xc9ae4858…6c68
0x34b655…2a6f
6 touches
3 conflicts
0x9e719c7a…df63
0x34b655…2a6f
6 touches
3 conflicts
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x5c10927c…58e5
0x34b655…2a6f
4 touches
1 conflict
0x60e0d54b…398f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity