← previous blocknext block →recent activity
Analyzing
Block #84,353,439
16 transactions · 13 stateful · 2026-06-29 00:08:32 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,353,439 · 16 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
1w08w010w111w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfe15fba…4f97
0x34b655…2a6f
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0xd31d33b6…a1a5
0x065c9d…c394
4 touches
1 conflict
0x00edf8ee…c588
0x065c9d…c394
3 touches
1 conflict
0x7d45e6da…da6f
0x065c9d…c394
3 touches
1 conflict
0x9791a1ae…a722
0x065c9d…c394
3 touches
1 conflict
0x0a82ef74…6501
0x34b655…2a6f
2 touches
0 conflicts
0x454d8940…cfe7
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 0xcfe15fbaf6…e24f97
Audit this contract →
← previous block·next block →recent activity