← previous blocknext block →recent activity
Analyzing
Block #84,348,947
14 transactions · 13 stateful · 2026-06-28 23:38:33 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,348,947 · 14 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
1w03w04w16w010w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x6498d0ae…2883
0x34b655…2a6f
4 touches
1 conflict
0xe1ee7bd2…bf39
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0002
0xe5bf0f…7139
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 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity