← previous blocknext block →recent activity
Analyzing
Block #84,258,068
13 transactions · 9 stateful · 2026-06-28 13:33:00 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,258,068 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9668681f…af08
0x34b655…2a6f
4 touches
1 conflict
0xb59003c4…98c5
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xc9fe0433…7f01
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x4ec9ff52…e6f7
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 0x9668681fd2…caaf08
Audit this contract →
← previous block·next block →recent activity