← previous blocknext block →recent activity
Analyzing
Block #84,027,137
19 transactions · 18 stateful · 2026-06-27 11:54:57 UTC
Parallelism
74/100
Blocked
28%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,027,137 · 19 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
4w05w18w09w012w113w214w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd77e6c1…264b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9e23e004…c73c
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x98fc5672…13c7
0x34b655…2a6f
6 touches
3 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
6 touches
3 conflicts
0xde08018b…f3be
0x34b655…2a6f
6 touches
3 conflicts
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 0xfd77e6c174…b2264b
Audit this contract →
← previous block·next block →recent activity