← previous blocknext block →recent activity
Analyzing
Block #84,319,941
24 transactions · 21 stateful · 2026-06-28 20:25:16 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,319,941 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w19w010w111w012w014w216w117w218w119w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e739938…e7ab
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4bdcc5ee…7e90
0x34b655…2a6f
4 touches
1 conflict
0x75194ada…a1c5
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xb40122dc…9d76
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xec85756f…0ba2
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
3 conflicts on slot 0x8e739938fe…14e7ab
Audit this contract →
← previous block·next block →recent activity