← previous blocknext block →recent activity
Analyzing
Block #84,316,812
19 transactions · 18 stateful · 2026-06-28 20:04:22 UTC
Parallelism
89/100
Blocked
22%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,316,812 · 19 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
3w04w19w010w011w115w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcc69dd9…d3f1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
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 0xbcc69dd9d2…10d3f1
Audit this contract →
← previous block·next block →recent activity