← previous blocknext block →recent activity
Analyzing
Block #84,357,093
11 transactions · 10 stateful · 2026-06-29 00:32:55 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,357,093 · 11 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
3w04w17w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6466bf77…19ac
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xb577e91d…1a81
0x34b655…2a6f
4 touches
1 conflict
0xc3464910…786f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd4b70e63…8718
0x34b655…2a6f
4 touches
1 conflict
0xea2f6fe4…63c9
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
1 conflict on slot 0x6466bf7729…eb19ac
Audit this contract →
← previous block·next block →recent activity