← previous blocknext block →recent activity
Analyzing
Block #84,324,316
12 transactions · 10 stateful · 2026-06-28 20:54:26 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,324,316 · 12 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
1w02w18w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x369a11e2…566f
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x99c320a0…b4a8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2496cf2c…1311
0x40c49f…2af0
2 touches
0 conflicts
0xf1fa5a16…c4eb
0x40c49f…2af0
2 touches
0 conflicts
0x46279ae7…20dd
0x69df8a…6292
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 0x369a11e278…dc566f
Audit this contract →
← previous block·next block →recent activity