← previous blocknext block →recent activity
Analyzing
Block #82,021,326
8 transactions · 8 stateful · 2026-06-18 04:42:11 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,021,326 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x8c962d08…9e24
0x34b655…2a6f
4 touches
1 conflict
0x75f56f28…1f99
0x065c9d…c394
2 touches
0 conflicts
0xf0f8c60d…8051
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000b
0x23c377…ea93
2 touches
0 conflicts
0x00000000…0000
0x24b18e…3301
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity