← previous blocknext block →recent activity
Analyzing
Block #82,049,209
14 transactions · 12 stateful · 2026-06-18 07:47:59 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,049,209 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w011w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9dc41da5…d506
0x065c9d…c394
3 touches
1 conflict
0x37d99953…5035
0x065c9d…c394
3 touches
1 conflict
0xe50545f6…4eea
0x065c9d…c394
3 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0x3439dfbcc6…080d03
Audit this contract →
← previous block·next block →recent activity