← previous blocknext block →recent activity
Analyzing
Block #84,698,818
37 transactions · 21 stateful · 2026-06-30 14:31:21 UTC
Parallelism
89/100
Blocked
48%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,698,818 · 37 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
1w02w13w05w18w09w117w018w122w023w124w226w228w029w133w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0806a61…8350
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x8b1b058b…0435
0x34b655…2a6f
6 touches
3 conflicts
0x146beb9f…4e34
0x34b655…2a6f
6 touches
3 conflicts
0x2484cc15…5afc
0x34b655…2a6f
6 touches
3 conflicts
0x2f358e74…1022
0x34b655…2a6f
6 touches
3 conflicts
0x79fade94…7f93
0x34b655…2a6f
6 touches
3 conflicts
0x91d9131f…0757
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xd0806a612a…fa8350
Audit this contract →
← previous block·next block →recent activity