← previous blocknext block →recent activity
Analyzing
Block #84,112,218
10 transactions · 9 stateful · 2026-06-27 21:21:47 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,112,218 · 10 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
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8d0e98f3…7ba0
0x34b655…2a6f
4 touches
1 conflict
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x1a4bf162…fa80
0x34b655…2a6f
4 touches
1 conflict
0x43f02fe0…f464
0x1b6862…e19c
2 touches
0 conflicts
0xb02fe354…948e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0000
0x1f86a9…17ed
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity