← previous blocknext block →recent activity
Analyzing
Block #82,262,429
20 transactions · 18 stateful · 2026-06-19 07:30:03 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,262,429 · 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
1w02w03w14w25w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af9143d…be5c
0x851145…3f07
6 touches
3 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x2ce2d49e…d185
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x851145ea…9f3f07
3 conflicts on slot 0x1af9143d77…21be5c
Audit this contract →
← previous block·next block →recent activity