← previous blocknext block →recent activity
Analyzing
Block #82,132,973
40 transactions · 33 stateful · 2026-06-18 17:07:00 UTC
Parallelism
88/100
Blocked
58%
Avg conflicts / tx
1.02
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,132,973 · 40 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
4w06w18w09w010w011w112w113w214w215w317w018w119w220w321w022w128w429w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xaa7ee7…f0e4
8 touches
6 conflicts
0x6c39ca5c…c750
0xd32edf…ff58
7 touches
6 conflicts
0x213a54fa…c85f
0x34b655…2a6f
6 touches
3 conflicts
0xafb2524a…0ce4
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity