← previous blocknext block →recent activity
Analyzing
Block #82,266,644
18 transactions · 16 stateful · 2026-06-19 07:58:19 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,266,644 · 18 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
1w02w13w14w25w08w09w111w215w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa5b76b…60db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xa174f91d…8097
0x065c9d…c394
4 touches
1 conflict
0x9827d287…4b00
0x851145…3f07
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x9ea5fca3…1089
0x34b655…2a6f
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
3 conflicts on slot 0x0aa5b76bf8…b060db
Audit this contract →
← previous block·next block →recent activity