← previous blocknext block →recent activity
Analyzing
Block #84,022,191
17 transactions · 13 stateful · 2026-06-27 11:22:02 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,022,191 · 17 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
1w02w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1c67a7d…b9b1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfd5ef2cf…02ae
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2c53a187…3646
0x34b655…2a6f
4 touches
1 conflict
0x8e730409…6b8e
0x34b655…2a6f
4 touches
1 conflict
0x3656f64f…87c3
0x40c49f…2af0
2 touches
0 conflicts
0x42dbce73…e417
0x40c49f…2af0
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 0xb1c67a7d65…cdb9b1
Audit this contract →
← previous block·next block →recent activity