← previous blocknext block →recent activity
Analyzing
Block #82,307,951
20 transactions · 18 stateful · 2026-06-19 12:33:39 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,307,951 · 20 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
1w02w03w04w16w27w08w117w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xa92c8763…6d7f
0x34b655…2a6f
6 touches
3 conflicts
0x97b0b2ee…4666
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5937bb0b…263b
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity