← previous blocknext block →recent activity
Analyzing
Block #82,020,731
10 transactions · 10 stateful · 2026-06-18 04:38:14 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,020,731 · 10 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
7w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc108f63d…204f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x513e200b…e0a1
0x065c9d…c394
2 touches
0 conflicts
0xcb4ed39a…7d6d
0x065c9d…c394
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
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 0xc108f63d12…17204f
Audit this contract →
← previous block·next block →recent activity