← previous blocknext block →recent activity
Analyzing
Block #82,731,950
28 transactions · 24 stateful · 2026-06-21 11:46:23 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,731,950 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w17w28w09w110w211w312w015w016w120w125w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1865516…fa1e
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x21e43e72…d2f6
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
6 touches
3 conflicts
0xfcb9138a…3830
0xc8689a…ee79
6 touches
3 conflicts
0x7a582f57…5b5a
0xd32edf…ff58
5 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
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 0xa18655162e…6dfa1e
Audit this contract →
← previous block·next block →recent activity