← previous blocknext block →recent activity
Analyzing
Block #84,362,541
15 transactions · 11 stateful · 2026-06-29 01:09:17 UTC
Parallelism
87/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,362,541 · 15 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
5w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0248ace7…371c
0x34b655…2a6f
2 touches
0 conflicts
0x18c610ca…b213
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity