← previous blocknext block →recent activity
Analyzing
Block #84,488,623
22 transactions · 19 stateful · 2026-06-29 15:09:46 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,488,623 · 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
1w02w14w05w16w28w39w110w211w013w014w116w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18ca6535…87c1
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x34bbb9df…e483
0x34b655…2a6f
4 touches
1 conflict
0x4795f7fe…217e
0x34b655…2a6f
4 touches
1 conflict
0x616ec3dd…5ce1
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xc458b1a7…eed4
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 0x18ca65353a…1c87c1
Audit this contract →
← previous block·next block →recent activity