← previous blocknext block →recent activity
Analyzing
Block #84,074,864
15 transactions · 13 stateful · 2026-06-27 17:12:46 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,074,864 · 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
4w05w18w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb30e1191…9e3c
0x34b655…2a6f
4 touches
1 conflict
0xb31b567f…387f
0x34b655…2a6f
4 touches
1 conflict
0x0c969dde…6b06
0xa6afd3…d132
4 touches
1 conflict
0x3e9f2190…ea5c
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3da49e5d…8067
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x438be73f…bf75
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 0xb30e119129…4f9e3c
Audit this contract →
← previous block·next block →recent activity