← previous blocknext block →recent activity
Analyzing
Block #84,592,921
12 transactions · 12 stateful · 2026-06-30 02:45:44 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,592,921 · 12 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
2w03w14w15w07w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f93f2f0…6666
0x34b655…2a6f
8 touches
6 conflicts
0xaa6e8631…015f
0x34b655…2a6f
6 touches
3 conflicts
0x16457580…3387
0x34b655…2a6f
4 touches
1 conflict
0x29d36d6f…4f1e
0x34b655…2a6f
4 touches
1 conflict
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x3f75fb9e…0d2e
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x5ea1cb70…6bb4
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
6 conflicts on slot 0x7f93f2f081…846666
Audit this contract →
← previous block·next block →recent activity