← previous blocknext block →recent activity
Analyzing
Block #84,598,004
14 transactions · 13 stateful · 2026-06-30 03:19:32 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,598,004 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w211w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x274b85f7…c526
0x34b655…2a6f
6 touches
3 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x97fe3267…5e87
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xa7acb855…97d2
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x86a6e399…369e
0x34b655…2a6f
4 touches
1 conflict
0x8a81fe6e…7fa9
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
3 conflicts on slot 0x274b85f751…f5c526
Audit this contract →
← previous block·next block →recent activity