← previous blocknext block →recent activity
Analyzing
Block #84,025,872
11 transactions · 8 stateful · 2026-06-27 11:46:32 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,025,872 · 11 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0020cef4…3ffc
0x34b655…2a6f
4 touches
1 conflict
0xd3e2e5a6…2b5c
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x4d76af31…03c7
0x34b655…2a6f
2 touches
0 conflicts
0x4d76af31…03c8
0x34b655…2a6f
2 touches
0 conflicts
0x6c98ebd9…ca13
0x34b655…2a6f
2 touches
0 conflicts
0x87f7111a…b2ab
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 0x0020cef4ef…203ffc
Audit this contract →
← previous block·next block →recent activity