← previous blocknext block →recent activity
Analyzing
Block #82,737,378
21 transactions · 16 stateful · 2026-06-21 12:22:36 UTC
Parallelism
86/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,737,378 · 21 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
2w03w110w015w116w018w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8e507257…71c1
0x34b655…2a6f
4 touches
1 conflict
0xc161f043…845c
0x065c9d…c394
2 touches
0 conflicts
0xf0331f49…103e
0x065c9d…c394
2 touches
0 conflicts
0x557cd4fa…228c
0x2a68ba…90c5
2 touches
0 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity