← previous blocknext block →recent activity
Analyzing
Block #82,263,408
22 transactions · 19 stateful · 2026-06-19 07:36:40 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,263,408 · 22 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
1w02w03w18w09w111w113w217w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x9cc13b7b…c0ac
0xa6afd3…d132
6 touches
3 conflicts
0x70638c24…1553
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x7bc74ef3…0fee
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity