← previous blocknext block →recent activity
Analyzing
Block #84,363,256
22 transactions · 21 stateful · 2026-06-29 01:14:03 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,363,256 · 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
1w02w18w09w110w214w315w016w119w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7500c6c7…6b90
0x34b655…2a6f
6 touches
3 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
6 touches
3 conflicts
0x44843215…109b
0x34b655…2a6f
5 touches
3 conflicts
0x2b2dce58…2f1d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x967c1b78…d187
0x34b655…2a6f
4 touches
1 conflict
0xcbee7652…8ff8
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity