← previous blocknext block →recent activity
Analyzing
Block #82,537,164
21 transactions · 17 stateful · 2026-06-20 14:02:44 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,537,164 · 21 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
1w02w03w06w19w111w013w116w117w218w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x8576e574…d51d
0x5afd3e…7620
4 touches
1 conflict
0x023f2a86…61b1
0x5afd3e…7620
4 touches
1 conflict
0xd5a3236b…6b26
0x34b655…2a6f
4 touches
1 conflict
0xb2fa1675…4e07
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity