← previous blocknext block →recent activity
Analyzing
Block #84,510,198
21 transactions · 21 stateful · 2026-06-29 17:33:45 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,510,198 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w011w013w117w218w319w420w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfff39462…a61b
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0xea6b3a0b…db4f
0x34b655…2a6f
4 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
4 touches
1 conflict
0xd89f212d…2bbf
0x34b655…2a6f
4 touches
1 conflict
0x23edc5f5…60d3
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
3 conflicts on slot 0xfff3946255…51a61b
Audit this contract →
← previous block·next block →recent activity