← previous blocknext block →recent activity
Analyzing
Block #84,136,684
14 transactions · 11 stateful · 2026-06-28 00:04:41 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,136,684 · 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
7w08w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19bfb0e5…73b4
0x34b655…2a6f
4 touches
1 conflict
0x2a42bfa9…6d80
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8e739938…e7ab
0x34b655…2a6f
4 touches
1 conflict
0x99910689…8959
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb40122dc…9d76
0x34b655…2a6f
4 touches
1 conflict
0xf997c4c7…617d
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
1 conflict on slot 0x19bfb0e559…d673b4
Audit this contract →
← previous block·next block →recent activity