← previous blocknext block →recent activity
Analyzing
Block #82,269,401
9 transactions · 9 stateful · 2026-06-19 08:16:43 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,269,401 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60c7217a…8c94
0x34b655…2a6f
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x71d34cdf…03aa
0x065c9d…c394
4 touches
1 conflict
0x349404c4…0b17
0x065c9d…c394
3 touches
1 conflict
0x88eb2d6b…7470
0x065c9d…c394
3 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x60d07066…695c
0x34b655…2a6f
2 touches
0 conflicts
0x8d0dd5c7…bd75
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x60c7217a29…038c94
Audit this contract →
← previous block·next block →recent activity