← previous blocknext block →recent activity
Analyzing
Block #84,040,357
13 transactions · 11 stateful · 2026-06-27 13:23:01 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,040,357 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x571cb36d…3b3d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf01ade5b…abeb
0x34b655…2a6f
4 touches
1 conflict
0x85ac0ab8…a3d8
0x34b655…2a6f
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x571cb36db3…a33b3d
Audit this contract →
← previous block·next block →recent activity