← previous blocknext block →recent activity
Analyzing
Block #82,552,924
23 transactions · 16 stateful · 2026-06-20 15:47:57 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,552,924 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w27w211w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0xa119a927…a6b7
0x065c9d…c394
3 touches
1 conflict
0xc69c39ec…ac98
0x065c9d…c394
3 touches
1 conflict
0xd8f12384…403a
0x40c49f…2af0
2 touches
0 conflicts
0x2f74f175…9285
0x69df8a…6292
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 0x8b305a3b6b…0c1c35
Audit this contract →
← previous block·next block →recent activity